I would say this is a problem of samba, not CUPS. CUPS being a network daemon(which AFAIK use protocol similar to HTTP, i.e. no persistent socket) should be expected to come and go at any time. Some kind of periodic polling routine is needed in samba if automatic CUPS printer discovery is a feature of samba. If samba notice the change of smb.conf for printer/share definition changes, it should notice the comes and go of CUPS service(the network port availability, not process ID).
--- Steve Langasek <[EMAIL PROTECTED]> wrote: > On Wed, Jul 06, 2005 at 07:05:05AM +0200, Christian > Perrier wrote: > > > Hmmm, we'll try to deal with this. Kenshi, as > the CUPS thing > > > maintainer, could you look at #315017 at some > moment. > > > > In short, samba fails to use CUPS printers when > it is started "too > > > quickly" after CUPS is started (both start at > "level 20" in init.d). > > > > This may also break other things which use CUPS > after it is started, > > > so this is probably not really specific to > samba. > > > I think we should consider reassigning this bug to > the cupsys package > > with something like "CUPS printing services are > not available > > immediately afer the daemon is started". > > > Strictly speaking this should be RC as "this > breaks unrelated > > software". > > I disagree. It's my understanding that this is a > longstanding bug in samba > for failing to sanely poll cups for information > about available print > queues. Even if cupsys *was* changed to only return > from the init script > after the printer lists have been made available, > smbd still has a bug in > not handling changes to the CUPS printer list. > > -- > Steve Langasek > postmodern programmer > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
