Yes, this system has been continuously upgraded from older Ubuntu
versions (starting with 9.04). It acts as a print server for the
office. I've no memory of manually setting up xinetd for cups-lpd. I
always assumed it was pulled in automatically as a dependency.
/etc/xinetd.d/printer looks like this:
service printer
{
socket_type = stream
protocol = tcp
wait = no
user = lp
server = /usr/lib/cups/daemon/cups-lpd
}
It took some digging through my changelogs and etckeeper history, but
now I'm certain that this file was generated by update-inetd calls from
/var/lib/dpkg/info/cups-bsd.postinst:
update-inetd --add 'printer stream tcp nowait lp
/usr/lib/cups/daemon/cups-lpd cups-lpd'
IIRC the only reason I have cups-bsd installed is that I was used to
typing 'lpq' to see if there are any jobs stuck in the print queue.
For the record, I don't see any cups-lpd processes actually running, so I don't
think things like the printers configured in my cups configuration should
affect xinetd's shutdown times.
Attempts to strace -f service xinetd restart show two things:
- the bug is not 100% reproducible for me
- systemctl restart talks to systemd over a socket, so I can't see any of the
interesting bits with strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750387
Title:
xinetd fails to restart during unattended upgrades
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/1750387/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
