Carlos E. R. wrote:
It could be the nscd daemon, it is configured to do that. Did you say which version of suse runs the server? It is weird, because that daemon crashes quite often, it is buggy as hell.
Thus, in your situation, "rcnscd restart" should have worked as well.
To which all I can do is respond by saying "OMG"!! That scares the devil out of me! Caching passwords seems like it is going to create a LOT of confusion, I could ask why? but not sure I really want to know! I am running SuSE 11.0 on the server. I had troubles with 11.1 so dropped back to 11.0 as I could not have that machine down for very long...
Maybe you can configure the print server not to request password from the client machines - depends on your needs, maybe being on your local network is enough auth.
Ok I am attempting to follow your suggestion, and the path seems to have lead me deeper and deeper into the quagmire of PAM... According to the documentation, there are files under /etc/pam.d/ and each one handles the authentication process for the service for which they are named, AND there is a file called cups. So I started to mess around with this file, setting it up to deny all logins, accept any login etc and NOTHING I do to this file seems to have any affect on authentication when I invoke the lp command. Many of these service files don't directly specify how and what modules to use for the authentication process, instead they include a common file called common-auth (which is a link for some odd reason to another file in this same directory called common-auth-pc) so I put in a debug switch there for the pam.unix2.so module and that showed me that it was getting invoked to do authentication for su (super user) but not for cups!! So I tried to fool around with the SU authenticator file and again I could not affect the authentication process for lp and cups.. I don't understand how or why the debug messages are showing up and I am confused about how CUPs and PAM are working together... So bottom line is I am not having much luck figuring out how to turn off the request for a password for CUPS and client machines...
I will fool around with setting up a full CUPs system on my client machines again, now that I understand the password issue a little better, and see if I can make headway....
It will be interesting to learn of your further investigations :-)
So far, in a word PAINFUL! Thanks again Carlos for your thoughts, I will plug away at it some more tomorrow, too tired myself to continue on tonight... Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org