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

[derekshaw]

re #44,45,46

Apologies in advance if I've mis-understood the interactions here.

Can you please post the preferred workaround?

I have this exact issue in a fully-patched lucid (10.04.2) deployment
that has already chewed up hours of my time over the past week. It
started with VMware ws7 not being able to use a 2nd PCI parallel port,
which, after my dis-belief passed, pushed me to kludge it with samba and
cups and raw print queues, only to find this bug (after 3 or 4 cold
starts to confirm yet another WTF?! moment). All I really want is for
smbd to start after cups, in a way that won't come back and bite me in
the [ah] when the packages get updated in the future (at a remote client
site)

I don't plan to test the proposed patch as described in #49, since this
machine is going into production ASAP (see comments about hours of time
invested over a week)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/494141

Title:
  CUPS starts after SAMBA; printers are not available (convert cups to
  upstart)