[cups.general] [cups.development] [RFE] STR #3344: Cups rewrites configuration files.

[Michael Sweet]

On Sep 25, 2009, at 1:13 AM, Johannes Meixner wrote:
> ...
> In contrast the header in /etc/printcap is
> ------------------------------------------------------------------
> # This file was automatically generated by cupsd(8) from the
> # /etc/cups/printers.conf file.  All changes to this file
> # will be lost.
> ------------------------------------------------------------------
>
> I would like to suggest to add such a header for all config files
> which are overwritten by the cupsd so that in the end all
> those config files could have the same header of the form
> ------------------------------------------------------------------
> # Configuration file for CUPS v1.3.11
> # This file was automatically generated
> # by cupsd(8) on 2009-09-24 15:15
> # Manual changes to this file will be ignored and lost.
> ------------------------------------------------------------------
>
> Should I file an enhancement STR for this?

Yes, this is a great suggestion!  In fact, I would go ahead and make  
it a P2 bug since a) we aren't changing any functionality and b) this  
is a common source of confusion for some users.

> ...
> Therefore I think the CUPS 1.4 documentation for all config files
> which are overwritten by the cupsd should be improved as follows:
> ---------------------------------------------------------------------
> If you do choose to edit this file manually, you will need
> to stop the scheduler before you start to edit it
> (see DirtyCleanInterval in the cupsd.conf documentation)
> and start the scheduler after you finished editing.
> ---------------------------------------------------------------------
>
> Should I file another enhancement STR for this?

Put it all in one bug, please.  And thanks!

___________________________________________________
Michael Sweet, Senior Printing System Engineer



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cups.org/pipermail/cups/attachments/20090925/51ad4ca9/attachment-0001.html>