Control: tags -1 moreinfo
Hi Peter,
On 16.05.2014 02:22, Peter Gervai wrote:
Package: clamav-daemon
Version: 0.98.1+dfsg-5
Severity: normal
--- /etc/init.d/clamav-daemon 2014-04-24 08:13:03.000000000 +0200
+++ /etc/init.d/clamd2 2014-05-16 02:15:17.939141376 +0200
@@ -320,7 +320,7 @@
done
if [ -z "$RUN_SUPERVISED" ] ; then
log_daemon_msg "Starting $DESC" "$NAME "
- start-stop-daemon --start --oknodo -c $User --exec $DAEMON
--pidfile $THEPIDFILE
+ start-stop-daemon --start --oknodo -c $User --exec $DAEMON
--pidfile $THEPIDFILE -- -c $CLAMAVCONF
ret=$?
else
log_daemon_msg "Starting $DESC" "$NAME (supervised) "
Why should this be necessary?
CLAMAVCONF=/etc/clamav/clamd.conf is the default location, where clamd
looks for a configuration file. Or did you change CLAMAVCONF and if so, why?
Apart from that it isn't quite LSBish that the initscript bails out
when config is
set to foreground and there's no 'daemon' installed, even on help or status
requests. It's pretty impolite towards a clusering infrastructure for example.
I'm not aware of any 'help' request that the init script should handle,
and for the status request, the error message gives the status, i.e.
that there is a configuration problem.
Or what status message would you expect in that case?
Best regards,
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
