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]
