Submitted By: Zoran Vasiljevic (vasiljevic)
Summary: Server instance controller process
Initial Comment:
Since some time we have added an option to nsd to fork
twice instead of once when putting itself in the background.
This way we have created one additional server instance
which is now
+-- On May 31, Zoran Vasiljevic said:
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
On 2003.05.31, Rob Mayoff [EMAIL PROTECTED] wrote:
Wouldn't it be better to run nsd as an NT service?
Do services automatically restart when they abnormally terminate?
I think that's what Zoran's trying to accomplish, here.
-- Dossy
--
Dossy Shiobara mail: [EMAIL
On 2003.05.31, Rob Mayoff [EMAIL PROTECTED] wrote:
Why not just use daemontools?
I haven't used daemontools yet, but does running nsd under daemontools
require you to run nsd -f? Or, will daemontools monitor the PID of nsd
and do the right thing if nsd disappears?
-- Dossy
--
Dossy Shiobara
On 2003.05.31, Zoran Vasiljevic [EMAIL PROTECTED] wrote:
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
On Saturday 31 May 2003 18:31, you wrote:
Why not just use daemontools? You avoid the race conditions of pidfiles
and get several other useful features.
Because of the added complexity of maintaining and setting up
different piece of software. We use just one nsd instance in our
solution and
+-- On May 31, Dossy said:
I haven't used daemontools yet, but does running nsd under daemontools
require you to run nsd -f? Or, will daemontools monitor the PID of nsd
and do the right thing if nsd disappears?
You use -f.
--
AOLserver - http://www.aolserver.com/
To Remove yourself
Dossy wrote:
I haven't used daemontools yet, but does running nsd under daemontools
require you to run nsd -f? Or, will daemontools monitor the PID of nsd
and do the right thing if nsd disappears?
It monitors the process, not the PID. If nsd dies, it restarts it, based
on starting it with 'svc
On Saturday 31 May 2003 18:43, you wrote:
How many lines of code and how many man-hours will it take to implement
in C? How long will it take to review all the code to ensure you've
neither introduced any new bugs or otherwise broken already existing
code?
We have it running for about 3
On Saturday 31 May 2003 19:07, you wrote:
nsd -s -t config.tcl
nsd -x -t config.tcl
(a typo).
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/
On Sat, May 31, 2003 at 07:07:18PM +0200, Zoran Vasiljevic wrote:
We have it running for about 3 years already. No need to develop anything
since it is already there. It does not change anything related to the main
server so it needs no extra testing.
It is just an C-equivalent of your
Andrew Piskorski wrote:
Zoran, I disagree.
Me too! It sounds like a more native way of controlling the process. I
can't count the number of cases of reported failure to properly install
and setup daemontools to work.
I don't like the alternative of using inittab, which requires root privs
to do
On Saturday 31 May 2003 20:03, Tom Jackson wrote:
Andrew Piskorski wrote:
Zoran, I disagree.
Me too! It sounds like a more native way of controlling the process. I
can't count the number of cases of reported failure to properly install
and setup daemontools to work.
Zoran, if votes count, I
13 matches
Mail list logo
