On Wed, Jul 06, 2005 at 10:04:10PM +1000, Andrew Bartlett wrote:
> On Wed, 2005-07-06 at 00:39 -0700, Steve Langasek 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
On Wed, 2005-07-06 at 00:39 -0700, Steve Langasek 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 pri
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
> Ya, I'd like to talk with new CUPS printing team. Lucky, all of them
> will be at Debconf5 :)
>
> Seriously, this bug relates with #309794.
>
> * cupsd hasn't own pid file.
> * it's hard to find `real' cupsd process without pid. Especially if multiple
> cupsd are running on some chroot.
> *
Hi,
I'm sorry for my late response.
At Wed, 6 Jul 2005 07:05:05 +0200,
Christian Perrier wrote:
> 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".
I fully agree this is
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 (b
> 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 thi
Quoting gary ng ([EMAIL PROTECTED]):
> yes, it is a timing problem. It is neither a bug of
> CUPS or Samba. However, since it is Samba quering
> CUPS, it can only be fixed/worked around by samba.
>
> restart samba after CUPS is properly up solved the
> problem. But that means something needs to be
yes, it is a timing problem. It is neither a bug of
CUPS or Samba. However, since it is Samba quering
CUPS, it can only be fixed/worked around by samba.
restart samba after CUPS is properly up solved the
problem. But that means something needs to be done to
delay the samba process. Of course, a lo
Quoting gary ng ([EMAIL PROTECTED]):
> Package: samba
> Version: 3.0.14a-3
> Severity: normal
>
> On my Xbox(64M, 733 Celeron), samba failed to query CUPS on bootup. This
> could be due to the fact that the resources is limited(and both CUPS and
> SAMBA is at S20) so when smbd is starting, CUPS ha
Package: samba
Version: 3.0.14a-3
Severity: normal
On my Xbox(64M, 733 Celeron), samba failed to query CUPS on bootup. This
could be due to the fact that the resources is limited(and both CUPS and
SAMBA is at S20) so when smbd is starting, CUPS has not fully up yet. I
only see 2 lines of error in
11 matches
Mail list logo
