-d option collision

[Phillip G Deneault]

I noticed that in the newest version of argus, the configuration file 
argus.conf sets up Argus running as a daemon process, however, the 
startup script also configures argus are a daemon process using the -d 
setting and this has the double-effect of making argus run in foreground 
mode.

Which is completely fine, except when one is trying to install argus and 
reboots the system for the first time, it hangs the booting process 
while Argus starts in user mode. :-)

I don't have an opinion which method is best, but can we pick one so we 
don't have this configuration glitch?  Or maybe just make it 'OR' rather 
than 'XOR'? :-)

Thanks,
Phil