David Sveningsson schreef:
Hi, I've written an application in c which I would like to start/stop as
a daemon in gnu/linux.
The application has the argument --daemon which forks the process and
exits the parent. Then it setups a SIGQUIT signal handler to properly
cleanup and terminate. It
David Sveningsson wrote:
Hi, I've written an application in c which I would like to start/stop
as a daemon in gnu/linux.
The application has the argument --daemon which forks the process
and exits the parent. Then it setups a SIGQUIT signal handler to
properly cleanup and terminate. It
Hi, I've written an application in c which I would like to start/stop as
a daemon in gnu/linux.
The application has the argument --daemon which forks the process and
exits the parent. Then it setups a SIGQUIT signal handler to properly
cleanup and terminate. It also maintains a lockfile (with
Hi,
You might consider D-BUS for your application and the D-BUS PHP binding
which is available since some days too. This would allow you to start /
stop your C application in a far more secure way than the suggested one.
Please have a look at my original release annoucement at the D-BUS
mailing
On Wed, Feb 27, 2008 at 7:51 AM, David Sveningsson [EMAIL PROTECTED] wrote:
Hi, I've written an application in c which I would like to start/stop as
a daemon in gnu/linux.
The application has the argument --daemon which forks the process and
exits the parent. Then it setups a SIGQUIT
@4u skrev:
Hi,
You might consider D-BUS for your application and the D-BUS PHP binding
which is available since some days too. This would allow you to start /
stop your C application in a far more secure way than the suggested one.
Please have a look at my original release annoucement at the
Per Jessen skrev:
David Sveningsson wrote:
Hi, I've written an application in c which I would like to start/stop
as a daemon in gnu/linux.
The application has the argument --daemon which forks the process
and exits the parent. Then it setups a SIGQUIT signal handler to
properly cleanup and
David Sveningsson wrote:
Per Jessen skrev:
So obviously something is catching the SIGQUIT before it gets to your
daemon. You mention a php site, so I take it you're running
apache.
In an apache process you then do an exec(something). I think apache
is probably taking care of the SIGQUIT.
8 matches
Mail list logo