You are not logged in.
Pages: 1
With the new release of Cups 2.0.0 today, the way it interacts with Systemd has also changed, as cups has added native systemd support finally. However, currently many of us have enabled "cups.service", which is no longer valid.
If you are using the testing repo, it is reccomended during install of the new cups to remove "cups.service" > sudo systemctl disable cups.service
Looking at the bugreport for adding full systemd support: "I've called the service "org.cups.cupsd" since at some point I think I'll add an org.cups.cups-lpd service as well - this mirrors what we've done for OS X and launchd, and eliminates the dependency on xinetd for LPD server support."
I have tried enabling "org.cups.cupsd" in systemd and it seems to work as intended. I have not tried "org.cups.cups-lpd", as I do not use a lpd printer.
TL;DR
With the new Cups 2.0.0 release, disable "cups.service" in systemd and enable "org.cups.cupsd"
I don't really know what I'm doing.
Offline
Moving to [testing]...
Offline
Hi, after disabling cups.service in systemd, I still found deadlinks to cups.socket and cups.target in /etc/systemd/system/...
Would you please write something for this update in the CUPS wikipage? So users like me could do sufficient manual changes and purge the trash files if any. Thanks!
Offline
Hi, after disabling cups.service in systemd, I still found deadlinks to cups.socket and cups.target in /etc/systemd/system/...
Would you please write something for this update in the CUPS wikipage? So users like me could do sufficient manual changes and purge the trash files if any. Thanks!
+1
Offline
If you disabled cups.service before doing daemon-reload or rebooting (like pacman told you to), it should have removed the other files as well.
Offline
I've reconfigured a remote printer (via SMB), but somehow it's not printing anymore, although the logs don't seem to show any kind of error... any ideas?
Diogo Baeder
http://diogobaeder.com.br/
Offline
Pages: 1