explodec14 has asked for the wisdom of the Perl Monks concerning the following question:
Hello -
I have posted my problems in the chatterbox but i didn't get replies satisfying.I have written a daemon (using Proc::Daemon:Init) which listens to port 9000 and forks whenever a client connects. So far so good. I have added signal handler in order to handle SIGHUP in case the user changes the configuration file and wants to reload the daemon. In this case, the daemon should restart itself in order to listen on the new configured port. The daemon traps the signal and when it tries to restart itself (using the exec call) it vanishes ...
I suspect it has to do with the daemonizing because otherwise I checked and it works fine.
(a) Why is that ?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Perl Daemons and SIGHUP
by moritz (Cardinal) on Feb 24, 2010 at 12:36 UTC | |
by explodec14 (Novice) on Feb 24, 2010 at 12:58 UTC | |
by moritz (Cardinal) on Feb 24, 2010 at 13:09 UTC | |
by explodec14 (Novice) on Feb 24, 2010 at 13:19 UTC | |
by mje (Curate) on Feb 24, 2010 at 13:33 UTC | |
| |
|
Re: Perl Daemons and SIGHUP
by cdarke (Prior) on Feb 24, 2010 at 13:56 UTC | |
by explodec14 (Novice) on Feb 24, 2010 at 14:58 UTC | |
by cdarke (Prior) on Feb 24, 2010 at 17:24 UTC | |
by explodec14 (Novice) on Feb 27, 2010 at 18:42 UTC |