unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Chmielewski <christopherchmielewski@fastmail.com>
To: help-guix@gnu.org
Subject: clamav freshclam - how to provide /etc config in general
Date: Tue, 30 Jan 2024 23:13:07 -0500	[thread overview]
Message-ID: <8b6b7b1b-a4d6-4213-b33d-57a04bba4c96@fastmail.com> (raw)

Hello Guix Hackers :)

I'm new to Guix and I ran into the following error running the freshclam 
command:

ERROR: Can't open/parse the config file /etc/clamav/freshclam.conf

Now I understand that the error is that the config file is not present 
in /etc. However I figure that there is a "guix-way" of providing this 
config file instead of just creating it in /etc (which would be lost on 
reboot).

So my question is more general. How do you provide config files for 
software that expects it to be located in /etc? Is there a best practice?

Thanks,

Chris


             reply	other threads:[~2024-01-31 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31  4:13 Christopher Chmielewski [this message]
2024-01-31 21:51 ` clamav freshclam - how to provide /etc config in general Carlo Zancanaro
2024-02-02  0:18   ` Christopher Chmielewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8b6b7b1b-a4d6-4213-b33d-57a04bba4c96@fastmail.com \
    --to=christopherchmielewski@fastmail.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).