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). Currently, /var/run/krb5kdc.pid and
> /var/run/kadmind.pid are hard-coded (and don’t use ${prefix} either).
Hm, why did you use open and write instead of fopen and fprintf? It would
have saved some code to use stdio, I think.
I suspect that upstream is going to want this to be a command-line option,
which would also resolve how to specify where to write the PID file,
rather than changing the default behavior.
I'm not sure what makes the most sense to do in the event of an error
writing out the PID file. I usually just log an error and continue in the
case of something like that rather than exit fatally. But upstream can
always change that as they incorporate the patch.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
