Re: [cups-devel] [LOW] STR #3067: State information belongs in /var/lib/cups, not /etc/cups

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

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

[STR Unresolved]

One thing I haven't been able to find... what's the downside to living with
the existing state of affairs (cups daemon updating /etc/cups/*.conf files
with timestamps and what not) and mounting /etc read-only anyway.  What
happens if cupsd trys to modify an /etc/cups file but can't due to a
read-only filesystem?  That's a similar effect to trying to maintain a
no-timestamp patch, although a read-only /etc may have a problematic effect
on other fields than timestamp fields (some day, if not today).

On a side note, is there a way to lock a cups config file so I can edit it
by hand and not worry about interfering cupsd (or experiencing problems
form cupsd interfered with me)?  Just killing the daemon while doing
editing would sort of work but is not very satisfying, especially on a
multi-user system.

Link: https://www.cups.org/str.php?L3067
Version: 1.3.9
Fix Version: Will Not Fix
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJWuhm8AAoJENujp6sI12Ij7f8QALF542yB3ZQs2BZuaRflRxfg
3sE9q+OYkxa9y2QsWPsBVebmj3XlvWgiPCPxN+r4gyo72aEpTKyTrWcwANMSvCsx
xB4NuJZg6KpGBMTnT+804W7Xf+A8ZzojrwTYaZjWYS3mzM0yqSuKUXP9xZGP3PwQ
AU/qFpb1/dmCMeJCs5sRfS+bQwEavRPV4eXUtP1GM8P8aN+bTKIT7pCKT4zmtl8j
ugXGPXLkVP6/H54Ll2DG2Q6Vm9QVzBhZXLihV7hbURv5BamrlVRHlaxsfo1SA9XM
VkR1cojvEt98jBohtVoaYpkA67gR4zuuvZJm5tfDF+n5O0Vaj976dl0K8meDifhC
Wz5eL2KPTvZmNth+blNOqgpnUCxpzFC7jBiaLOv0auNINP2DKGSfYjuEhIaUfIbW
rru3OWwzJe9wPd77ZTZRDC8V1wZEr4PKZpXS6AaXusGijxCQMfuLo21JfcL+PLkt
ItIii9XVe92zhA5dCFerp15VcXHFkm22ySqE3O7Aa7SVfdMP+ywzrT5zeOz24r9I
YYe3V+f4TknmNSHvZbE+FaYUXkTbkaUO2TwC2zXhP4s0fllK6AM9Z2IjINQR9uPT
P0MhRQxK04F5iSM5rhKGy9mPIMJISO4l6M9WHTjf1lgEZH3/4hSiOx2viJqswBR5
BG6FdBVgYDJfPxBnCXMK
=cUsA
-----END PGP SIGNATURE-----