For the first time, clamd (cvs) died and did not wake up, even though I use daemontools. Nothing in the log, no core dump.. nothing.
For experts with daemontools, is there a way to capture other data outputted bt clamd other than the ones that go to the logfile?
I don't know how you've set up your clamav to run with daemontools, but you can normally setup the run script to redirect stderr to stdout, and then create a related logging process using multilog to capture the stdout and stderr of clamd into logfiles.
Something like this should work with daemontools >= 0.76:
#!/bin/sh # run script for clamd exec 2>&1 exec /path/to/clamd
and then create a directory, /service/clamd/log
which has a run script as follows:
#!/bin/sh exec multilog t ./main
And then all the stdout and stderr of clamd will go to multilog, which will create a directory called main, and write automatically rotated and timestamped logfiles in there.
-- Anand
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
