Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Thu, 30 Aug 2007, Matthew Gillen wrote: > Scott Ehrlich wrote: >>> This will take care of it, but there is an easier way, use the >>> yppasswd(1) rather than passwd(1). >> >> I've tried both. >> >> I've now discovered that ypcat passwd on the server returns new test >> accounts, but a client machine that is able to log into an existing yp >> account, does not reflect the new accounts... >> >> Would using pdbedit this morning for samba security lockdowns have any >> impact? > > Using nscd would. Try disabling that service on your clients. If you tried > to log in to a client, then created the account on the server, the nscd daemon > would remember the previous "no such user" answer instead of checking with the > server again. > > Matt Not caching anything (by choice) so that service is not running. Suggestions always welcome. Thanks. Scott > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > Discuss mailing list > Discuss-mNDKBlG2WHs at public.gmane.org > http://lists.blu.org/mailman/listinfo/discuss > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |