You are not logged in.
Hello,
after the last cups update, cups doesn't start any more backgrounded (with "@cups" in the daemons line in /etc/rc.conf). I did not find any entry in the log files for that. Before the cups update, I used to start cups backgrounded for faster booting. After I removed the "@", everything is ok again.
Why does cups not start backgrounded any more?
Dieter
Offline
It is working for me mostly. Do you use turboprint? There is a thread with a warning about versions < 1.90. I am usint 1.83 and I notice cups sometimes dies, I havent bothered to look into it yet.
Offline
Yes, I use turboprint, too. But I have the actual version 1.93 and the problem occurs definitely after the recent update of the Arch cups package. I haven't had a problem with a dying cups - after the update cups doesn't start any more. Replacing "@cups" by "cups" in the daemons line of /etc/rc.conf did it.
Offline
Cups causes problems again randomly. From time to time it either does not start during boot or it dies (Arch32). I use a licensed version turboprint for my Canon printer which is not supported directly by cups (thanks, Canon).
Does anybody else have problems with cups, too (with or without turboprint)? The problems with cups on my system started in December; before that I haven't had problems with cups and turboprint. I know that another player in this area is ghostscript which may cause problems with cups/turboprint.
Offline
you could try to disable the cups udev rule that restarts it if a usb printer is turned on.
Offline