Rainer Zocholl said: > [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.
And a distraction. > >>> 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! ;-) The phrase "Don't fork into background" is not a verb phrase - it is a state. The state is either enabled or disabled. Having said that, I do get the impression that English may not be the first language of some of these hard working coders. I've taken this to mean "Run as daemon - Default: yes". Again, we're talking about state. I don't care for implicit responses such that no response implies the default, but that's what we have > > Why don't you write: > # Fork into background. > # Default: enabled > #Foreground or: # Run mode ::= Daemon or Foreground # Default is Daemon # Foreground Daemon Where the BNF allows (and I think should require) one of Daemon or Foreground. And where is the BNF, anyway? Notice that absent the comments in any of this, the keyword Foreground has no context and loses a great deal of clear purpose. That's a bad thing. Better? RunMode = Daemon # define run mode as foreground or background And yes - I do like optional studly caps as it becomes more readable, as in: TheVirtualBarAndGrill.com vs thevirtualbarandgrill.com dp dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
