[EMAIL PROTECTED](Rob MacGregor) 17.12.05 09:48
>On 17/12/05, Shahzad Abid <[EMAIL PROTECTED]> wrote: >> >> Hi All >> >> I am running clamd integrated with qmail on FC3, problem is that >> when i start clamd manually it starts working and a continues debug >> log is generated on the shell Konsole when I close that shell >> Konsole clamd stops working. "nohup" would solve that but is only a workaround. >> I put clamd in startup, this hangs my system when i boot the system. >Version of clamav? >Did you uncomment either of the following lines in clamd.conf: ># Don't fork into background. ># Default: disabled >#Foreground Beg your pardon. What is the meaning of "disabled don't fork into background"? Will it be forked or not? You have 0,3 sec to decide! ;-) Why don't you write: # Fork into background. # Default: enabled #Foreground (Assuming the oposit of the default is "Foreground" so it becomes easier to switch.) Almost good: ># Enable debug messages in libclamav. ># Default: disabled >#Debug What is the meaning of "disabled enabled debug messages in libclamav"? Are debug messages generated or not? (it's not as hard as the above example) Why don't you write: # libclamav generates debug messages # Default: disabled #Debug Configuration of clamavd is difficult enough, why making it more complicate by using double negations? Rainer _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
