[cups.general] /etc/printcap not regenerated with restart of cupsd on linux

Norm Jacobs Norm.Jacobs at Sun.COM
Mon May 12 21:14:27 PDT 2008

I am going to guess that the version of CUPS that you are running was 
built with '--with-printcap=/var/run/cups/printcap'. I don't know why 
you would have an /etc/printcap that is older, unless you had upgraded 
from an older version that was built '--with-printcap=/etc/printcap'. 
Since I took a look at a system that I have running Ubuntu and it has 
both /etc/printcap and /var/run/cups/printcap, with the /var/run version 
being newer, it appears that might be the case for me. I didn't see 
anything else on my system that looked to be generating /etc/printcap. 
If you want /etc/printcap to reflect the current set of queues in CUPS, 
you can symlink /etc/printcap to /var/run/cups/printcap or change your 
cups config (in /etc/cups/cupsd.conf) to include a Printcap 
/etc/printcap entry. Ideally, you would simply remove /etc/printcap, 
identify applications that are parsing /etc/printcap, and work to fix 
them to use the CUPS API for print queue enumeration.


Alex Janssen wrote:
> Is the printcap file in /etc on Linux supposed to be regenerated each 
> time /var/run/cups/printcap changes and cupsd is restarted?
> Thanks,
> Alex

More information about the cups mailing list