|go ahead... be a heretic|
Re: Closing stdout on CGI early. - how better to start daemon?by pmas (Hermit)
|on Aug 31, 2001 at 17:33 UTC||Need Help??|
My solution will be to use database - I am a database guy...;-)
When you want another process to handle something, delegate: write in some table parameters of what needs to be done, and set status to 'Scheduled'. Then, "boss" process is done and can return.
Later "boss" process can check status of tasks scheduled (you may sort them by userID or something), and even try to re-schedule rejected tasks (after fixing error).
Database transactions will handle all record locking.
Does it make sense? It plan to use something like that in my system later, not now (so no code right now, sorry).
Can you monks with expertise in Apache tell me what is better method (less resorce hog) to run "subordinate": all the time (without need to start new process), sleeping some time, or via cron, requiring to start new process occasionally. I understand it is a trade-off, what will be the guidelines for right decision?