Bug#315017: samba: failed to query CUPS on boot
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. Kenshi, let's note we have to talk about this in Debconf... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315017: samba: failed to query CUPS on boot
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 signature.asc Description: Digital signature
Bug#315017: samba: failed to query CUPS on boot
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 bug of cupsys. Kenshi, let's note we have to talk about this in Debconf... 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. * in default, cupsd forks soon. It means value of first cupsd pid (refered by start-stop-daemon -m) is meaningless. * cupsd can foreground mode using -F option, but we couldn't know when is cupsd really ready. I want to avoid modifing upstream source as I can, but I think this needs modifing upstream source. Thanks, -- Kenshi Muto [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315017: samba: failed to query CUPS on boot
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. * in default, cupsd forks soon. It means value of first cupsd pid (refered by start-stop-daemon -m) is meaningless. * cupsd can foreground mode using -F option, but we couldn't know when is cupsd really ready. So, well, we should then reassign it to cupsys package, right ?
Bug#315017: samba: failed to query CUPS on boot
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]
Bug#315017: samba: failed to query CUPS on boot
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 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. I understand we now poll, btw... Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Samba Developer, SuSE Labs, Novell Inc.http://suse.de Authentication Developer, Samba Team http://samba.org Student Network Administrator, Hawker College http://hawkerc.net signature.asc Description: This is a digitally signed message part
Bug#315017: samba: failed to query CUPS on boot
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 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. I understand we now poll, btw... Ah, hurrah. :) Do you know which version this was fixed in? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#315017: samba: failed to query CUPS on boot
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 has not fully up yet. I only see 2 lines of error in the smbd log saying connecting to CUPS refused. This leave the server fails to share any print resources. I This sounds strange as the CUPS init script is actually started before the samba daemons. Could it be a timing problem, meaning that CUPS stuff is not ready when the samab processes start immediately after? If so, I would rather call this a bug in cupsys. What happens when you manually stop then restart samba after the system boot is finished? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315017: samba: failed to query CUPS on boot
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 longer term solution is have it done periodically within samba. both CUPS and samba is now at S20, almost at the same time. I have changed CUPS to S19 but it still doesn't help. Mainly because there is still no delay. --- Christian Perrier [EMAIL PROTECTED] wrote: 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 has not fully up yet. I only see 2 lines of error in the smbd log saying connecting to CUPS refused. This leave the server fails to share any print resources. I This sounds strange as the CUPS init script is actually started before the samba daemons. Could it be a timing problem, meaning that CUPS stuff is not ready when the samab processes start immediately after? If so, I would rather call this a bug in cupsys. What happens when you manually stop then restart samba after the system boot is finished? __ 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]
Bug#315017: samba: failed to query CUPS on boot
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 done to delay the samba process. Of course, a longer term solution is have it done periodically within samba. both CUPS and samba is now at S20, almost at the same time. I have changed CUPS to S19 but it still doesn't help. Mainly because there is still no delay. 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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315017: samba: failed to query CUPS on boot
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 the smbd log saying connecting to CUPS refused. This leave the server fails to share any print resources. I need to manually do a start/stop of samba. Are there any way to tell samba to periodically retry the probing of CUPS rather than just at startup ? -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.31-xbox-chimpanzee-vs-ll Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages samba depends on: ii debconf [debconf-2.0] 1.4.30.13Debian configuration management sy ii libacl1 2.2.23-1 Access control list shared library ii libattr12.4.16-1 Extended attribute shared library ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libcomerr2 1.37-2sarge1 common error description library ii libcupsys2-gnutls10 1.1.23-10Common UNIX Printing System(tm) - ii libkrb531.3.6-2 MIT Kerberos runtime libraries ii libldap22.1.30-8 OpenLDAP libraries ii libpam-modules 0.76-22 Pluggable Authentication Modules f ii libpam-runtime 0.76-22 Runtime support for the PAM librar ii libpam0g0.76-22 Pluggable Authentication Modules l ii libpopt01.7-5lib for parsing cmdline parameters ii logrotate 3.7-5Log rotation utility ii netbase 4.21 Basic TCP/IP networking system ii samba-common3.0.14a-3Samba common files used by both th -- debconf information: samba/nmbd_from_inetd: * samba/run_mode: daemons samba/log_files_moved: samba/tdbsam: false * samba/generate_smbpasswd: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
