Re: Why is clamd so hard?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This may be better posted to a clamav forum - but I want to try here (vent
a bit!) first.

In the past (Fedoras 6ish - 13) I have installed clamd from source because
I was frustrated with the slow speed of updates when a new version of clam
became available. However, this brough with it a raft of SELinux problems
and one of the comments on the SELinux list was "why don't you use the yum
repo version?"

Well, in upgrading to F15 I though I would give it a try...

Everything is in different places and called different things to what I
was used to but I am really stumped with this one:

When I try to start clamd with the "service clamd start" command systemd
fails and gives the very unhelpful detail "Process: 17780
ExecStart=/etc/rc.d/init.d/clamd start (code=exited, status=1/FAILURE)"
What the hell does status=1 mean?

So I try to start it from the command line:
ERROR: Can't open/parse the config file /etc/clamd.conf

Now here's the thing... /etc/clamd.conf is where the config file used to
be in F13 when I compiled from source, but this is a bare-metal install of
F15 with clam* installed through yum. The config file is now in
/etc/clam.d/clamd.conf

The /etc/init.d/clamd script simply has the following in it:
# cat /etc/init.d/clamd
======8<=============================================
#!/bin/bash
#
# chkconfig: - 75 35
# description: The clamd server running for <SERVICE>

CLAMD_SERVICE=clamd
. /usr/share/clamav/clamd-wrapper
======8<=============================================

and /usr/share/clamav/clamd-wrapper (which is symlinked to
/etc/init.d/clamd-wrapper) has this line in it:
CLAMD_CONFIGFILE=/etc/clamd.d/${CLAMD_SERVICE}.conf

Finally /etc/sysconfig/clamd has this in it:
# cat /etc/sysconfig/clamd
======8<=============================================
CLAMD_CONFIGFILE=/etc/clamd.d/clamd.conf
CLAMD_SOCKET=/var/run/clamd/clamd.sock
#CLAMD_OPTIONS=
======8<=============================================

Nowhere can I find any reference to /etc/clamd.conf - everywhere it seems
to be referenced as /etc/clamd.d/clamd.conf

So why does it fail with the message
ERROR: Can't open/parse the config file /etc/clamd.conf
???

So I guess I need to take this to the clamav-users list?

No-one here got clamd working with F15?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk3vTwYACgkQ75heFf3niHJmLgCgnxrr6WXkFFat0EWJPAREG6Fb
7/8Anjy/Iqyt1bj5WohgjjB2Q8lJ3vSZ
=3NVd
-----END PGP SIGNATURE-----

--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Relevant Pages

  • Re: [opensuse] How to Clamav and postfix
    ... life of my I cannot get amavis and clam to work well. ... If there's a howto w/out using amavis I'm all open for that too ... Start with clamd: ... If that works then configure amavisd-new as shown above and start the service: ...
    (SuSE)
  • Re: Ive had enough. Im starting a DNS blackhole list.
    ... 'k, I looked at clam way back, and just checked to reconfirm ... ... > databases, start clamd, uncomment the clamd section in amavisd.conf, ... > FreeBSD: The fastest and most stable server OS on the planet ...
    (freebsd-stable)