But you can just as well disable the pid file in cups. Disabling the
local socket is pretty evil, since that will immediately break all the
cups command line tools (you'd always have to specify "-h localhost").
Without the local socket there is no way that we can check when the
daemon is ready to accept requests, and the remainder of the script
won't work either.
** Changed in: cups (Ubuntu)
Importance: Undecided => Low
** Changed in: cups (Ubuntu)
Status: New => Triaged
** Summary changed:
- cups upstart post-start script not completing
+ cups upstart post-start script hangs forever when local socket is disabled
--
cups upstart post-start script hangs forever when local socket is disabled
https://bugs.launchpad.net/bugs/672438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
