[Bug 660535] Re: Samba [printers] section doesn't work

2011-04-03 Thread John Edwards
*** This bug is a duplicate of bug 494141 ***
https://bugs.launchpad.net/bugs/494141

Just to mention that smbd does *not* refresh CUPS printers every 750
seconds. You need to send it a reload (or SIGHUP) .

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660535

Title:
  Samba [printers] section doesn't work

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 660535] Re: Samba [printers] section doesn't work

2011-04-01 Thread John Edwards
This looks related to bug #494141, where Samba does not show CUPS printers 
because CUPS starts after smbd:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/494141/

A long term fix may be in the CUPS upstart configuration, but that
doesn't help people using Ubuntu 10.04 LTS where CUPS is still using a
SysV startup script instead of upstart. Some suggested workarounds for
Ubuntu 10.04 are given in that bug report.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660535

Title:
  Samba [printers] section doesn't work

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 660535] Re: Samba [printers] section doesn't work

2011-04-01 Thread Clint Byrum
*** This bug is a duplicate of bug 494141 ***
https://bugs.launchpad.net/bugs/494141

John interesting. I commented on bug #494141 as well about the lucid
situation.

It seems to me that it is in fact a duplicate of that bug.

Martin Pitt, in comment #30, says that the impact of the bug is
mitigated by the fact that smbd will attempt to refresh the printers
every 750 seconds. So while 12 minutes is a long time to wait, its not a
total loss. I think even my suggested solution is a bit large to put
into an SRU.

I'm going to mark this as a duplicate of that bug.

** This bug has been marked a duplicate of bug 494141
   CUPS starts after SAMBA; printers are not available (convert cups to upstart)
 * You can subscribe to bug 494141 by following this link: 
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/494141/+subscribe

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660535

Title:
  Samba [printers] section doesn't work

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 660535] Re: Samba [printers] section doesn't work

2011-02-04 Thread Clint Byrum
Hi Julio, thanks for taking the time to file this bug report and help us
make Ubuntu better!

Right, in natty cups has an upstart job. So we could make it:

start on ((filesystem or starting smbd)
   and (started dbus or runlevel [2345])
  and stopped udevtrigger)

But that will run us into the and problem when trying to stop/start
smbd, so we will need to use a waiter job. The waiter job can be
backported to use the init.d script in lucid and still function
properly.

Marking Triaged, as this only affects Ubuntu and its clear what the
problem is. Setting Importance to Medium.

** Package changed: upstart (Ubuntu) = cups (Ubuntu)

** Changed in: cups (Ubuntu)
   Importance: Undecided = Medium

** Changed in: cups (Ubuntu)
   Status: New = Triaged

** Tags added: lucid upstart

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660535

Title:
  Samba [printers] section doesn't work

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 660535] Re: Samba [printers] section doesn't work

2010-10-14 Thread Julio Cesar Gazquez
Did I put upstart as the affected package? Sorry, it should be cups!

-- 
Samba [printers] section doesn't work
https://bugs.launchpad.net/bugs/660535
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