Am 26.05.2010 08:34, schrieb Török Edwin: >Looks like clamd stopped, that usually happens with terminal output. >Shouldn't happen with nohup though. > >Type 'fg' to bring it to foreground, and see why it stopped.
I did so, here is the result: ======================= h830101:/etc # nohup /usr/local/sbin/clamd & [1] 9227 [1]+ Stopped nohup /usr/local/sbin/clamd h830101:/etc # fg nohup /usr/local/sbin/clamd nohup: appending output to `nohup.out' ======================== And the contents of nohup.out show nothing suspicious: ======================== h830101:/etc # cat nohup.out Limits: Global size limit set to 104857600 bytes. Limits: File size limit set to 26214400 bytes. Limits: Recursion level limit set to 16. Limits: Files limit set to 10000. Limits: Core-dump limit is 0. Archive support enabled. Algorithmic detection enabled. Portable Executable support enabled. ELF support enabled. Mail files support enabled. OLE2 support enabled. PDF support enabled. HTML support enabled. Self checking every 600 seconds. Listening daemon: PID: 9227 MaxQueue set to: 100 Client disconnected (FD 14) h830101:/etc # ========================= Thanks again for your attempts to help Mike _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
