[cups.development] [RFE] STR #2465: support writing a PID file

martin.pitt.canonical martin.pitt at canonical.com
Thu Aug 2 08:09:34 PDT 2007


DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

cups does not support writing an external pid file. This is necessary for
distributions, since init scripts cannot just go ahead and do a blunt
"killall cupsd". That would kill cupsds in chroots as well.

This patch adds a new configuration option PidFile, so it's completely
optional and does not change the default behaviour.

Wrt. your comment "This won't happen, since the contents of the file
cannot be assumed to be correct if cupsd aborts without deleting it",
that's clear of course. Standard init script behaviour is to verify that
the pid in the pid file is actually a running cupsd, so if cupsd was
killed, it won't accidentally kill another process with the same pid.

This is actually the same request as http://www.cups.org/str.php?L805, but
I am not able to attach any file or comment to it, so sorry for opening a
new one.

Link: http://www.cups.org/str.php?L2465
Version:  -feature
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 47_pid.dpatch
Type: application/octet-stream
Size: 2872 bytes
Desc: not available
URL: <http://lists.cups.org/pipermail/cups-devel/attachments/20070802/6ca153c3/attachment.obj>


More information about the cups-devel mailing list