On Saturday 07 April 2007 04:36, Verner Kjærsgaard wrote: > Lørdag 07 april 2007 02:26 skrev Doug McGarrett: > > On Wednesday 04 April 2007 05:24, Carlos E. R. wrote: > > [..] > > > Please somebody, tell me how to salvage this mess--in plain English, one > > step at a time. > > > > doug > > HI Doug and list, > > - let's do some stepwise debugging :-) > - first, it doesn't hurt to repeat the lppasswd entry, making dead sure > what one types in (as root): > > lppasswd -g sys -a doug
Aster adding your user login name (above is assumed that your login name is doug) restart cups as root with: rccups restart to reread configuration. CUPS stores user authentication information as configuration settings. Generally, in Linux background processes (demons) read configuration on start. If configuration is changed, they have to be stopped and started again. This is not done automatically as multiuser systems are not designed to interrupt other folk that is using system without good reason (server malfunction), or system administrator approval. I guess that some authentication shema exists that allows password change on the fly, with instant access with new password, but I don't know can CUPS use such functionality. > Now fire up your browser, goto http://localhost:631 > > Select manage printers > How many printers do you see? > Are they green or red, what does their status say? ... -- Regards, Rajko. http://en.opensuse.org/Portal -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
