-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Todd Denniston wrote:
> If I am somewhat more patient, after ~30 seconds from the kill
> command, cvs
>
>[any command] will terminate. It looks like the client processes another
>30-50 files after the server is given the SIGTERM, which seems like a
lot of
>files to me.
>
>I am going to change my plan a little and issue the SIGTERM a couple of
times,
>sleep 30 seconds and then issue `killall -9 cvs`, so if there is some
kind of
>emergency we are able to go down in under a minute.
This really shouldn't be the case and I cannot reproduce it. I would
really love to see a reproducible case if you can provide a short script
or the like that creates one.
Are you sure that new servers are not starting up between when you issue
the killall and look for new processes? Try taking inetd down before
issuing the killall.
You do mention 30 seconds - that's how long CVS waits for locks by
default, but I don't think this should be a problem. I think SIGTERM
should wake your processes from their sleep to exit.
Derek
- --
*8^)
Email: [EMAIL PROTECTED]
Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
iD8DBQFAbhvkLD1OTBfyMaQRAqVlAJ4zzFadYy8Kr7T3eJc2a0KyvYmJvACcDDUk
I8UscY0Rds8wVQBiyCBFXFI=
=j/pW
-----END PGP SIGNATURE-----
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
