It's also worth noting that if you're capturing SIGTERM, you're capturing your chance to for your process to die while cleaning up its mess. Normally the "please restart" signal is SIGHUP. If someone has to do maintenance on these systems and kill -TERMing your processes doesn't work it's going to head right on to kill -9 which may or may not be a desirable state of affairs.
On 6/21/06, Jake Good <[EMAIL PROTECTED]> wrote:
I also have that code in my Rails apps on DH.
It works so far... seems kinda hokey, but if it works for now.
Gary Shewan wrote:
> On 21 Jun 2006, at 13:47, Koen Van der Auwera wrote:
>
>
>> I can confirm this. I'm also running typo at dreamhost.
>>
>
> That's good to know, not just me then.
>
>
>> I use feedburner and as you probably know feedburner warns you when
>> there is something wrong with your sourcefeed. So in fact you know
>> when there's a problem with your blog.
>>
>
> Heh, actually I didn't know. But I do now. People trying to leave
> commments email me and I check logs ... I'll look at that though.
> But it's a good point to note that a 500 error can be thrown up when
> somebody tries to leave a comment ... and Feedburner won't let you
> know about that ... will it?
>
>
>> Before I had about 20+ messages/warnings a day and since I added
>> the piece of code below I see about 2 to 3 messages a week or so.
>> Big improvement if you ask me.
>>
>
> Agreed ... it's a big relief.
>
> G
> _______________________________________________
> Typo-list mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/typo-list
>
>
_______________________________________________
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list
_______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
