[Bug 300019] New: clamd fails silently at startup when /dev/ null is not writeable
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=300019 Summary: clamd fails silently at startup when /dev/null is not writeable Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: max@novell.com ReportedBy: suse-beta@cboltz.de QAContact: qa@suse.de Found By: --- I have found an interesting bug in clamd ;-) root@karawane:/home/cb> rcclamd start Starting Clam AntiVirus daemon done root@karawane:/home/cb> rcclamd status Checking for Clam AntiVirus daemon unused Nothing in the logs. To make the story short, here's the reproducer: chmod 644 /dev/null rcclamd start # results in "done" rcclamd status # results in "unused" I had to use strace to find out what the problem was - and this is not fun at 3:00 AM after a failed kernel update... I don't expect that clamd works without problems in this case, but it should at least return $? != 0 ("failed") or print an error message. BTW: Don't worry about the broken /dev/null permissions - they are a bug at my hosting provider's rescue system. I'm also not sure what went wrong with the kernel update, so simply ignore it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=300019#c1 --- Comment #1 from Reinhard Max <max@novell.com> 2007-09-03 12:43:41 MST --- There are two ways to fix this, and I am not sure which one to take: 1. if /dev/null can't be opened, don't close FDs 0..2, so that output continues to go to the tty from which clamd was started, so that clamd will work, but clutter the terminal. 2. if /dev/null can't be opened, error out, because a system with unusable /dev/null is broken anyways. I tend to go for option 2, but will discuss it with the clamav folks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=300019 User max@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=300019#c2 --- Comment #2 from Reinhard Max <max@novell.com> 2007-12-14 07:15:46 MST --- Reported to the ClamAV team: https://wwws.clamav.net/bugzilla/show_bug.cgi?id=729 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=300019 User max@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=300019#c3 Reinhard Max <max@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #3 from Reinhard Max <max@novell.com> 2008-01-31 10:46:45 MST --- Upstream accepted a modified version of my patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com