1 |
I think I have run into this problem in the past but in a different |
2 |
way. I found some upgrade processes would fail and a strace pointed |
3 |
to libnss_nis.o. To work around it I would temporally remove the nis |
4 |
entry from my/etc/nsswitch.conf file. |
5 |
|
6 |
My problems have cleared up over the past year. I attributed them to |
7 |
bugs in libnss_nis. |
8 |
|
9 |
I have not run into your specific problem. I seldom reference UID's |
10 |
that are not in my NIS system or in the local /etc/password file. |
11 |
|
12 |
Good luck, |
13 |
|
14 |
Steve Herber herber@×××××.com work: 206-221-7262 |
15 |
Security Engineer, UW Medicine, IT Services home: 425-454-2399 |
16 |
|
17 |
On Wed, 26 Oct 2005, Weicheng Pan wrote: |
18 |
|
19 |
> Hi all: |
20 |
> I meet a very strange problem on my NIS. I test two cases, which one is |
21 |
> a Gentoo i386 box, and the other is Gentoo AMD64 box. |
22 |
> I referenced this page: |
23 |
> http://www.linux-nis.org/nis-howto/HOWTO/settingup_client.html , and can |
24 |
> successfully login. |
25 |
> |
26 |
> But when my directory has unknown UID on AMD64 box, it will return a |
27 |
> SEGMENTATION FAULT error. |
28 |
> |
29 |
> Then I use the following code to verify the client settings: |
30 |
> |
31 |
> Finally, I found that getpwnam() call will cause segmentation fault |
32 |
> rather than return NULL on pass a non-exist username on AMD64 box. |
33 |
> |
34 |
> Is anybody has encounter this situation? |
35 |
> |
36 |
> Regards, |
37 |
> Weicheng. |
38 |
> |
39 |
> -- |
40 |
> gentoo-amd64@g.o mailing list |
41 |
> |
42 |
-- |
43 |
gentoo-amd64@g.o mailing list |