I'd appreciate a clue as to what's going on: since today's update (sid on two IBM laptops), neither clamd nor freshclam will start. The error message changes according to the directory from which the command /etc/init.d/clamav-daemon or /etc/init.d/clamav-freshclam is given. Here's a sample:
root@/etc/init.d# /etc/init.d/clamav-daemon restart Stopping ClamAV daemon: clamd. Starting ClamAV daemon: clamd /sbin/start-stop-daemon: Unable to chdir() to= '/etc/init.d' (No such file or directory) failed! root@/usr/sbin# /etc/init.d/clamav-daemon restart Stopping ClamAV daemon: clamd. Starting ClamAV daemon: clamd /sbin/start-stop-daemon: Unable to chdir() to= '/usr/sbin' (No such file or directory) failed! I'm stumped. I'd worry less, except that a third laptop, also updated today, does NOT show this problem. Help would be gratefully accepted. P.S. A second problem appeared when I tried to send this message via mutt: Here's the error message: gpg: skipped "99421A63": secret key not available gpg: signing failed: secret key not available Press any key to continue... (So I'm sending this note viat Yahoo! Apologies.) -- johnrchamp...@columbus.rr.com ---------------------------------------------------- GPG key 1024D/99421A63 2005-01-05 EE51 79E9 F244 D734 A012 1CEC 7813 9FE9 9942 1A63 gpg --keyserver subkeys.pgp.net --recv-keys 99421A63 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
