Red Hat Bugzilla – Bug 241628
clamav-server-sysv is not usable after install
Last modified: 2007-11-30 17:12:05 EST
Description of problem: Several flaws in clamav-server-sysv need correcting after installation for it to be usable. Version-Release number of selected component (if applicable): clamav-server-sysv.i386 0.88.7-2.fc6 How reproducible: Always. Steps to Reproduce: 1. yum install clamav-server-sysv 2. 3. Actual results: # chkconfig clamd-wrapper --add service clamd-wrapper does not support chkconfig Expected results: # chkconfig clamd-wrapper --add # chkconfig clamd-wrapper --list clamd-wrapper 0:off 1:off 2:on 3:on 4:on 5:on 6:off Additional info: Why is there a depends in clamav-server for clamav-server-sysv? Seems it should be the other way around...
Patch to give clamd-wrapper chkconfig support. diff -Naur clamd-wrapper /usr/share/clamav/clamd-wrapper --- clamd-wrapper 2004-11-07 22:10:52.000000000 -0600 +++ /usr/share/clamav/clamd-wrapper 2007-05-28 23:56:23.000000000 -0500 @@ -1,7 +1,7 @@ #!/bin/bash # -# Xchkconfig: - 75 25 -# Xdescription: The clamd daemon listens for incoming connections on \ +# chkconfig: - 75 25 +# description: The clamd daemon listens for incoming connections on \ # Unix or TCP socket and scans files or directories on demand. test "$CLAMD_SERVICE" || {
... and make the script executable: chmod u+x /usr/share/clamav/clamd-wrapper
... and with the "test" of an unset var as the first line, the script is unusable anyway: # service clamd-wrapper start *** /etc/init.d/clamd-wrapper can not be called in this way *** Please see /usr/share/doc/clamav-server-*/README how *** the clamav-server can be configured
this is not intented to be executed; it provides functionality like /etc/init.d/functions. See mentioned README for details.
In that case, please rename it to clamav-server-wrapper or something. As compared to clamav-milter-sysv which *is* usable after install, and would *not* have wasted my time ^*&#ing around with it before getting to a "README". Also, /etc/init.d/functions is there because the system expects it to be there. The same with halt and single. When I see any other script "foo" installed in /etc/init.d, I expect "foo" to be a usable service. Period. Besides, the README already covers copying clamd.int to /etc/init.d. Lastly, what does this say about "usability", to have packages install that do nothing but point to a README? I mean come on, I see you've made it flexible, and that's fine, but why not install it with a pre-determined service running from the start? Is this too much to ask?