Upstream here, finally. Sorry about the delay replying to this issue,
I've been juggling no less than three different jobs and have been spending
my free time this last week playing with Greg Strong's excellent ChessV
program (http://sourceforge.net/projects/chessv) to help research a
Chess variant that I've "invented" (Schoolbook Chess).
Anyway, enough of the excuses and let me look at this issue.
All zoneserver processes are correctly killed when using the upstream
zoneserver process killer. The script in question has this bit of
code:
ps -ef | awk '{print $2":"$8}' | grep zoneserver | grep -v $$ | \
cut -f1 -d: | xargs kill > /dev/null 2>&1
English translation: Send a term signal to all processes running on
the machine with the name zoneserver
This is followed by:
ps -e | awk '{print $1":"$NF}' | grep zoneserver | grep -v $$ | \
cut -f1 -d: | xargs kill -9 > /dev/null 2>&1
So my script doesn't have this issue.
Now, in terms of the patch for the zoneserver that has the zoneserver
also be able to kill its own children, I agree this is a good idea.
However, the patch is too big a change for the current stable branch,
1.2.12. I don't know if getpgrp(), setpgrp(), and killpg() exist
on all systems MaraDNS' zoneserver is supposed to compile on (Mac OS X,
the *BSDs--though Adam Montage has given me an account I can do OpenBSD
testing on, Solaris, etc). What I will do is make this a change for
the 1.2.13 release of MaraDNS which will come out one of these days.
I appreciate Boris submitting this patch to MaraDNS.
Now, in terms of MaraDNS progress, I'm slowly but surely working on the
BIND to CSV2 converython script. You can see my progress here:
http://www.maradns.org/download/1.2/snap/200609/
Anyway, thanks guys for your interest in MaraDNS. This is, from where
I am sitting, WONTFIX for the 1.2.12 branch, but the patch will be
applied in 1.2.13.
- Sam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
