Cups printer sharing needs restart to work

[Peter Jensen]

Binary package hint: cupsys

Sorry if this is a duplicate, but i saw no bug reports regarding cups on 7.10.

When sharing a printer with cups, it not available to the client machines.
If however, cups is restarted, the printer is available to the clients. The printer is a well supported Brother hl-2030

The solve this i added the cups servers IP to the client machines /etc/hosts.

Is this a bug or lag of information?

[colchaodemola (colchaodemola)]

I have exactly the same problem, after a server reboot clients can not see the shared printer
I tried to change cups to S99 in startup folder but it didn`t work.
My solution was add /etc/inid.d/cupsys restart in rc.local, so cups is started by the system scripts and is restarted by rc.local.

[Peter Jensen (peterjensen84)]

I found a "Cleaner" solution:-)
Add the cupsserver ip to your /etc/hosts file.
That did it for me

[colchaodemola (colchaodemola)]

i really don`t think that`s a clean solution.
For example, if i change the server ip i will have to update all clients.
And if i have , let`s say 300 clients [not all of them with ssh enabled] i will have a few problems to change hosts in each one.
restart cups in rc.local seems not cleaner , but a smarter solution :)

[Peter Jensen (peterjensen84)]

Oh i can see that.
But for the standard home user, i still think that adding the ip i best.
But, perhaps the best solution would be, if the Ubuntu devs, corrected the bug:-)

[Till Kamppeter (till-kamppeter)]

This is caused by an upstream bug in CUPS. CUPS stops broadcasting if it gets a HUP signal for reloading its configuration. This happens every night via the logrotate cron job and a full stop and restart of CUPS is required to get broadcasting back. See bug 173470.

[Hugues Fournier (hugues-fournier)]

This problem can be linked too to the fact that CUPS 1.3.x has a regression : it only detects/lists network interfaces, IPs and netmasks at startup (instead of the normal way of operation that is to regularly poll for changes in the list of network interfaces, IPs and netmasks)
The consequence is that any interface appearing after CUPS is started, will have its corresponding network not considered as local even if it is a local network : it will refuse any connection from this network, and a local printer will not be shared on it.
See bug 177075.