|
Bugzilla – Full Text Bug Listing |
| Summary: | nscd broken after upgrade to glibc-2.4.90 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Forgotten User OS1JNCFbCX <forgotten_OS1JNCFbCX> |
| Component: | Basesystem | Assignee: | Petr Baudis <pbaudis> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | andreas.hanke, jmolles, michael.brasse, ro |
| Version: | Alpha 4 plus | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User OS1JNCFbCX
2006-09-26 07:03:31 UTC
BTW: This is the standard nsswitch configuration for local (file) authentication. Does logging on other accounts work? Can you please run nscd with the -d switch and paste the (relevant) output here? "logging on other accounts"? You mean "login"? Yes, all other accounts don't show this problem. The following is said by nscd when doing "su -": 17250: handle_request: request received (Version = 2) from PID 17258 17250: GETFDPW 17250: provide access to FD 4, for passwd 17250: handle_request: request received (Version = 2) from PID 17258 17250: GETFDGR 17250: provide access to FD 6, for group Petr: I see the same on chomsky with my NIS account. I had to stop nscd to be able to log in as skh, login as root worked fine. if you get nscd to really modify it's cache, you can get it to work with a running nscd as well, but the problem can occur again. Note that "nscd restart" or "system reboot" does not necessarily fix the problem, but for example changing something in /etc/passwd and reloading nscd works to fix nscd's cache. *** Bug 208392 has been marked as a duplicate of this bug. *** Fallout from http://sourceware.org/ml/glibc-cvs/2006-q3/msg00114.html, the assertion in __nscd_getgrouplist (initgr_resp->ngrps > 0) is no longer valid. Fixed. *** Bug 209323 has been marked as a duplicate of this bug. *** |