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]
