in reply to Re: Re: Monitoring after fork && exit
in thread Monitoring after fork && exit
fork && exit; open FH, ">logfile" or do{system("logger", "Boom!"); die} print FH "Look ma, I'm logging\n"; etc....
If that doesn't hit the logfile then check the usual culprits... disc full etc.
Personally I'd be checking what the user did, rather than the script. I'd suspect the user of hitting Ctrl-C or something, or closing the terminal before the fork.
In any case, you should consider using 'cron' or 'at' to run scheduled tasks rather than sleeping until midnight - what happens if the system admin reboots the machine?
____________________
Jeremy
I didn't believe in evil until I dated it.
|
|---|