That seems like a good approach to me.
First, we would want to change the order of operations a bit so we fork (both
times) before loading the database. I'm pretty sure that as it is written now,
it loads over 500MB worth of signature database content into RAM and then
forks, temporarily result
Hi Micah,
Can you not have a two part demon process. Part one fork's the real
demon and then waits for it to die (with 'wait()').
On death of the child, it cleans up and exits. Yes I know it is not
quite as simple as that. It will have to have signal handlers etc. to
kill the child etc. and sh
