"Jeff Johnson" <[EMAIL PROTECTED]> wrote:
> The print "." fixed the problem where the socket took 30 seconds to
> after shutdown before the port could bind again. No load required, I
> just start, stop, attempt restart which would fail with a socket bind
> error. Not even in daemon mode.
You're right, I did get this in Webware when I did a quick
start/restart... it was more around less than 4-5 seconds, though it
was unpredictable.
OTOH, on another box where I have a daemon script, I put in this code
for shutdown:
stop)
echo -n "Shutting down WebKit: "
kill -s 2 `cat $PID_FILE`
for SUBPID in `ps aux --cols 200 | grep 'python Launch.py' | awk
'{print $2}'` ; do
kill -s 2 $SUBPID > /dev/null 2>&1
done
success "Shutting down WebKit"
echo
;;
and I haven't had any problem. Otherwise it simply wasn't killing all
the processes, or threads, or whatever they were. There's actually
only one of the "python Launcy.py" processes that needed to be killed
(after which all of the others were killed)... but it wasn't happening
before I did this.
I typically restart this daemon rather quick (just webkit restart,
which takes around 2 seconds maybe), and haven't had a problem since I
changed this.
Ian
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
