I got to launch it again, so I have finish with a cron job like
*/10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups
but it is a dirty solution. I have no idea of what make it stop.
NB: I have seen problems related to apparmor, this machine has no apparmor package.
after 6 minutes or so, cups is not responding.
it do not produce error on the log, just stop working, worse, it exit with 0
⌌—————— ——————— ——————— ——————— ——————— ——————— ——————— ——————— ——————— ——————— ——————— ——————— ——⌍ system/ cups.service; enabled; vendor preset: enabled)| /usr/sbin/ cupsd -l (code=exited, status=0/SUCCESS) | ——————— ——————— ——————— ——————— ——————— ——————— ——————— ——————— ——————— ——————— ——————— ——⌏
|root@cupsmachine :~# systemctl status cups |
|● cups.service - CUPS Scheduler |
| Loaded: loaded (/lib/systemd/
| Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago |
| Docs: man:cupsd(8) |
| Process: 28686 ExecStart=
| Main PID: 28686 (code=exited, status=0/SUCCESS) |
| |
|juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. |
⌎——————
I got to launch it again, so I have finish with a cron job like
*/10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups
but it is a dirty solution. I have no idea of what make it stop.
NB: I have seen problems related to apparmor, this machine has no apparmor package.