forwarded 550781 http://krbdev.mit.edu/rt/Ticket/Display.html?id=6618
thanks
Michael Stapelberg michael+db20090...@stapelberg.de writes:
You can find the patches attached to this mail. Please have a look if
they work for you. What is still missing is a way to specify the
destination folder
I'll argue in the upstream discussion that this should be a default
behavior change where failure to write the pid file is non-fatal.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Michael Stapelberg michael+db20090...@stapelberg.de writes:
You can find the patches attached to this mail. Please have a look if
they work for you. What is still missing is a way to specify the
destination folder using autoconf (I’m not good at autoconf, so this
would take me a long time).
Hi,
Excerpts from Russ Allbery's message of Mi Nov 04 20:02:12 +0100 2009:
If you have time, it would probably be faster for you to do it. I can
submit it upstream and see about getting it incorporated there afterwards
(and we can carry it in the Debian package until the next release if
Russ, thoughts on this?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Russ,
Excerpts from Russ Allbery's message of Mi Nov 04 00:08:52 +0100 2009:
You can use the -n option for that.
The -n option to start-stop-daemon does not create a PID file. It changes
the matching logic for finding the process to kill (to use logic that
isn't allowed by Debian
Sam Hartman hartm...@debian.org writes:
Russ, thoughts on this?
I'm reluctant to run daemons in non-forking mode when everyone else uses
the other mode. It feels like the right solution would be to teach those
daemons to write out their own PID files; that code is generally quite
simple and
Michael Stapelberg michael+db20090...@stapelberg.de writes:
Excerpts from Russ Allbery's message of Mi Nov 04 19:51:26 +0100 2009:
the other mode. It feels like the right solution would be to teach
those daemons to write out their own PID files; that code is generally
quite simple and most
Hi,
Excerpts from Russ Allbery's message of Mi Nov 04 19:51:26 +0100 2009:
the other mode. It feels like the right solution would be to teach those
daemons to write out their own PID files; that code is generally quite
simple and most long-running daemons have that capability for exactly that
I don't think start-stop-daemon can create the pid file because these process
fork and daemon themselves.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi,
Excerpts from Sam Hartman's message of Di Nov 03 19:47:53 +0100 2009:
I don't think start-stop-daemon can create the pid file because these process
fork and daemon themselves.
You can use the -n option for that.
Best regards,
Michael
--
To UNSUBSCRIBE, email to
Michael Stapelberg michael+db20090...@stapelberg.de writes:
Excerpts from Sam Hartman's message of Di Nov 03 19:47:53 +0100 2009:
I don't think start-stop-daemon can create the pid file because these
process fork and daemon themselves.
You can use the -n option for that.
The -n option to
Package: krb5-kdc
Version: 1.7dfsg~beta3-1
Severity: normal
krb5kdc and kadmind are running, but there is no corresponding pidfile in
/var/run. Thus I cannot use a program like monit to monitor these processes.
Please let start-stop-daemon create a pidfile for both daemons.
Best regards,
Michael
13 matches
Mail list logo
