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]
