public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Herber <herber@thing.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] NIS problem
Date: Fri, 28 Oct 2005 12:44:56 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0510281238280.8556@thing.com> (raw)
In-Reply-To: <435EA887.8090509@csie.nctu.edu.tw>

I think I have run into this problem in the past but in a different
way.  I found some upgrade processes would fail and a strace pointed
to libnss_nis.o.  To work around it I would temporally remove the nis
entry from my/etc/nsswitch.conf file.

My problems have cleared up over the past year.  I attributed them to
bugs in libnss_nis.

I have not run into your specific problem.  I seldom reference UID's
that are not in my NIS system or in the local /etc/password file.

Good luck,

Steve Herber	herber@thing.com		work: 206-221-7262
Security Engineer, UW Medicine, IT Services	home: 425-454-2399

On Wed, 26 Oct 2005, Weicheng Pan wrote:

> Hi all:
> I meet a very strange problem on my NIS. I test two cases, which one is
> a Gentoo i386 box, and the other is Gentoo AMD64 box.
> I referenced this page:
> http://www.linux-nis.org/nis-howto/HOWTO/settingup_client.html , and can
> successfully login.
>
> But when my directory has unknown UID on AMD64 box, it will return a
> SEGMENTATION FAULT error.
>
> Then I use the following code to verify the client settings:
>
> Finally, I found that getpwnam() call will cause segmentation fault
> rather than return NULL on pass a non-exist username on AMD64 box.
>
> Is anybody has encounter this situation?
>
> Regards,
> Weicheng.
>
> -- 
> gentoo-amd64@gentoo.org mailing list
>
-- 
gentoo-amd64@gentoo.org mailing list



      reply	other threads:[~2005-10-28 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 21:49 [gentoo-amd64] NIS problem Weicheng Pan
2005-10-28 19:44 ` Steve Herber [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0510281238280.8556@thing.com \
    --to=herber@thing.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox