Comments on: How not to restart mod_perl servers

By: Randolf Richardson

Randolf Richardson — Sat, 24 Jul 2010 01:24:39 +0000

I read about another solution once, but I don’t recall if it’s part of the standard set of modules. It involved having a “touch file” that would trigger a “Reload” operation whenever the timestamp on the “touch file” changed (any timestamp compares as different from a non-existing file as I recall).

This seems, to me, a reasonable solution even for a production environment.

Thanks for writing this interesting article.

By: Gracie

Gracie — Fri, 25 Jun 2010 13:29:35 +0000

You’re somewhat wrong about #2. If you are using a smart events-based notification Watcher with Catalyst, it sees every change you make. If you make a change before the server has restarted, it just kills it and starts over.

Right now this only works on Linux with Linux::Inotify2 installed. However, I know there’s work being done on a Mac fs events module for File::ChangeNotify. Once that’s on CPAN, you can just install it and get the same effect.

Other platforms like BSD and Solaris have their own FS events systems that could be hooked into as well.

By: Jonathan Swartz

Jonathan Swartz — Thu, 15 Apr 2010 09:01:09 +0000

originalgeek: You realize this is strictly for personal development use? None of this is meant for live production traffic.

By: originalgeek

originalgeek — Wed, 14 Apr 2010 16:45:39 +0000

#3 isn’t really a good idea, will cause your server to die from forkdeath unless if it receives more than moderate use.

By: Jonathan Swartz

Jonathan Swartz — Wed, 23 Sep 2009 12:37:25 +0000

Dave Rolsky: Ok, thanks for the update. Does the built-in Catalyst watcher use File::ChangeNotify, or are you talking about a separate third-party watcher?

By: Dave Rolsky

Dave Rolsky — Wed, 23 Sep 2009 02:39:39 +0000

Other platforms like BSD and Solaris have their own FS events systems that could be hooked into as well.