printers.conf getting overwritten

[Richard Cooke]

Tim, thanks for the reply. I set up all my local printers on a print server for all our Linux users to access. It is easier to manage one print server that it is to manage 14 client's print server. system-config-printer allows me that ability.

I tried setting up using http://localhost:631 on the server. That worked great as long as you were logged onto the server. Client machines could not access that printer though they could see the printer in their print manager.

I understand what the two commands you suggested are for:

1) chmod does not allow printconf-backend to be executed. Which is fine locally since I am the one to install/manage printers. However, our remote sites in 8 different states would not be able to add their own printers. Politically incorrect.

2) chattr does not allow the printers.conf file to be editted/overwritten at all. Again accomplishing the same thing as item 1 above.

Do you know if printconf-backend has a "Virtual Printer" as I have seen described in these forums? I can only specify a locally connected, Networked CUPS (IPP), Networked Unix (LPD), Networked Windows (SMB), Netowrked Novell (NVP) or a Networked JetDirect types of queues using printconf-backend.

Again, thanks for the reply. Didn't know about chattr.

Rich

> On Tue, 2006-11-28 at 11:52 -0500, Richard Cooke wrote:
> > 2) have CUPS not modify the printers.conf of existing printers,
>
> CUPS isn't doing it; system-config-printer is (printconf-backend).
>
> Add the queue using the CUPS web interface at http://localhost:631/ and
> 'chmod -x /usr/sbin/printconf-backend' or 'chattr
> +i /etc/cups/printers.conf'.
>
> Tim.