On Saturday 31 May 2003 17:56, you wrote: > My personal solution to this is to run the nsd process from a shell > script.
<snip> Doable, but messy. IMHO. nsd already takes care about pid-file logfiles, etc when going to background. This is all nice stuff and I wouldn't like to reimplement all this in an external shell-script. Why just not put this logic on the C-level in the nsd? It is already forking to background. Why not fork one more time and get a nice controller/worker tandem? > As I said, I think implementing this directly in code with a > user-selectable command line switch might be really convenient. But, > it's obviously not necessary to achieve the same results ... as you can > do it simply with a 8 line shell script. This is right. It is the convenience of having a well tested, working solution which you just use w/o shell-script workarounds. Somebody has to write, update, maintain, etc... this shell-script, right? Now, what I did not say (nor done yet, but I'm planning to) is: win32. You have no shell there. By having all built-in, you have no worry. Cheers, Zoran -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
