Re: [LOW] STR #4240: cups print queue name changes between reboots

While it is technically possible that you could cause corruption of printers.conf by rebooting or killing cupsd mid-update, but all versions of CUPS protect against this with varying degrees of paranoia.

However, this looks like the distro-supplied support software is deleting the queue when the printer is disconnected and creating the queue when the printer is reconnected.

On 2012-12-12, at 4:42 PM, Bo Z Nyus <[email protected]> wrote:

> On 12/12/2012 06:33 AM, Michael Sweet wrote:
>> DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
>> 
>> [STR Closed w/o Resolution]
>> 
>> This looks like your Linux distribution is deleting and then re-adding the
>> printer when the USB issues happen. And the default queue name is
>> different than the one you originally chose.
>> 
>> I'd talk with the Scientific Linux folks about what they are using to
>> automatically create/delete USB printers...
>> 
>> Link: https://www.cups.org/str.php?L4240
>> Version: 1.4.6
>> Fix Version: Third-party
>> 
> OK, I will let them know.  But I am wondering if it could be due to a 
> timing/integrity issue surrounding the cups configuration files. If CUPS 
> has the file open when it starts, and the host is rebooted before CUPS 
> closes it, perhaps one or more of its configuration files has lost 
> integrity by the time the system comes back up?
> 
> If so, then this could be a more generic problem.  OTOH, SL uses 1.4, 
> which is a bit downrev to begin with.   An upgrade might well address 
> this issue.
> 
> _______________________________________________
> cups-bugs mailing list
> [email protected]
> http://lists.easysw.com/mailman/listinfo/cups-bugs

________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair