On Wed, Mar 09, 2005 at 02:00:01PM +0100, Baltasar Cevc wrote:
>
> Generally speaking I see two classes of applications that could
> use the class I described:
> 1. network daemons
> 2. some daemons which have tasks that could be solved using cron
>(in a less elegant way)
>
> For the first, N
A. Pagaltzis wrote:
* Baltasar Cevc <[EMAIL PROTECTED]> [2005-03-09 14:45]:
would the solution be to extend something like Proc::Daemon or
to "downgrade" Net::Daemon (which seems more similar to what I
thought about).
I think ideally Proc::Daemon should be extended to cover all
common funct
* Baltasar Cevc <[EMAIL PROTECTED]> [2005-03-09 14:45]:
> would the solution be to extend something like Proc::Daemon or
> to "downgrade" Net::Daemon (which seems more similar to what I
> thought about).
I think ideally Proc::Daemon should be extended to cover all
common functionality, and Net::Da
Hi Randy,
thanks for your reply, - and for the anwer: it is no currently.
My mail was more to gather some idea first - some kind of
brainstorming - as I am not sure what the best solution is;
another point to clear first would for example be:
would the solution be to extend something like Proc::Da
Baltasar Cevc wrote:
One possibility would certainly be to "generalize" Net::Daemon
to something like a App::Daemon or Proc::Daemon (the latter
exists, but has only a limited functionality, concentrates just
on the "real daemonizing" and does not take care about PID etc.)
or something in that direc
Hi Flavio,
> See also: Net::Daemon
Thank you for the pointer - it should appear in that list -
however, at least I have some daemons not having any direct
connections to clients (a daemon that updates the different user
lists from one central data source, a daemon which updates the
iptables ruleset
> App::Control, Proc::PID::File, File::PID
See also: Net::Daemon
"The Net::Daemon class offers methods for the most
common tasks a daemon needs: Starting up, logging,
accepting clients, authorization, restricting its own
environment for security and doing the true work. You
only have to override
Baltasar Cevc wrote:
Hi everybody,
yesterday, when writing the core of another daemon intended to run
on one of the servers I administer, I caught myself copy-pasting
code from other daemons. Not some lines but more or less the whole
main part.
After a bit of thinking, I realized that there must be
> Proc::Daemonzier would take care of
> - creating a pid file
> - checking if the daemon is really running if the pid file exists
>(detection of stale pid files)
> - starting only if no instance is running
> - restart the daemon|signal him to reconfigure itself
>(see example)
Add relia
Hi everybody,
yesterday, when writing the core of another daemon intended to run
on one of the servers I administer, I caught myself copy-pasting
code from other daemons. Not some lines but more or less the whole
main part.
After a bit of thinking, I realized that there must be a better
solution. P
10 matches
Mail list logo
