Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
Upstream changes:
0.17
- add option: --backlog to change the backlog size (default: SOMAXCONN) (thanks to Yuryu)
0.16
- [bugfix] unset the environment variable when a file is removed from the directory specified by --envdir
0.15
- added option: --envdir for reloading configuration (thanks to limitusus)
- added options: --enable-auto-restart and interval for periodical automatic restarting (thanks to limitusus)
- added option: --kill-old-delay for delaying SIGTERM (thanks to limitusus)
0.14
- fix regression in 0.13; start_server wo. "--dir" was causing errors
0.13
- add option: --dir (thanks to kazeburo)
0.12
- bugfix: support for programs with whitespaces (thanks to clkao)
- add option: --signal-on-term (thanks to miyagawa)
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
Upstream changes:
0.07 Sat May 08 14:00:00 2010
- --port option is now omittable (so daemons _not_ binding to TCP ports (like FCGI servers binding to unix domain sockets) can be hot-deployied using Server::Starter)
Packages Collection.
It is often a pain to write a server program that supports graceful
restarts, with no resource leaks. The Perl 5 module Server::Starter,
solves the problem by splitting the task into two. One is start_server,
a script provided as a part of the module, which works as a superdaemon
that binds to one or more TCP ports, and repeatedly spawns the
server program that actually handles the incomming commenctions.
The spawned server programs under Server::Starter call accept(2)
and handle the requests.
