[Bug 494141] Re: CUPS starts after SAMBA; printers are not available (convert cups to upstart)

Steve Langasek steve.langasek at canonical.com
Mon Sep 13 17:39:25 BST 2010


Potential issues with the proposed patch:

  - this is a workaround in the smbd job, not a correct fix, which will need to be reverted later.
  - in the (rare) event that a user has stopped smbd manually and then changes runlevels, current upstart will give a weird hang waiting for a second local-filesystems event.
  - if someone has configured a loopback cifs share to be mounted at boot time, their system will hang at boot as a result of this change.

So there is regression potential here from the described change to the
smbd job, and I'm not really in favor of this approach.  Why has the
cups package now gone more than two cycles without being converted to an
upstart job, which would fix this properly?  Also, why does samba not
re-scan for a cups server?  That seems like unnecessarily unreliable
behavior on samba's part, and something that should be straightforward
to fix correctly (and suitable for an SRU).

-- 
CUPS starts after SAMBA; printers are not available (convert cups to upstart)
https://bugs.launchpad.net/bugs/494141
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.



More information about the Ubuntu-server-bugs mailing list