So you just toss SIGTERM at it and hope for the best? We can do that...
Mark Lim "Though my eyes are cold as ash,
Brightmail, Inc. my heart burns with fire."
415-365-6192 Traditional Japanese martial proverb
http://www.brightmail.com
On Thu, 27 Sep 2001, Peter Romianowski wrote:
> Hi,
>
> as far as I monitored this list the "preferred" mechanism is to kill the
> process.
> The original comment from Serge (was within a discussion about next
> version's features):
>
> "The next version does not have a more graceful shutdown method, although
> I'm
> pushing to get the next version released this month. Like I said, mail
> won't get lost or corrupted by a 'kill', so it hasn't been a high priority.
> It is more of a priority though so we can gracefully restart without having
> to stop and start the process."
>
> According to that I kinda rewrote the run.sh script so that it stores the
> PID of the process into a file. A second script (with the meaningful name
> "stop.sh" :-) reads this PID and kills the process. Works fine for me
> (especially for boot/shutdown).
>
> But a "graceful shutdown method" would be a real nice feature, 'cause I'm
> still feeling a bit uneasy killing the process... :-)
>
> cheers,
> pe.ro
>
> > How do folks generally shutdown james in a production (UNIX) environment?
> > Does it handle signals gracefully or is there a preferred mechanism?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
