supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: David Miller <dave@frop.net>
To: supervision@list.skarnet.org
Subject: Re: chpst -u -/ "unable to get password/group file entry"
Date: Wed, 6 Aug 2008 21:39:41 -0500	[thread overview]
Message-ID: <20080807023941.GA15934@pretender.frop.net> (raw)
In-Reply-To: <20080805145630.GX16519@ice.mudshark.org>

Thanks for the suggestion.

I wonder if you could give me some pointers on how to use strace and what to look for. I'm not very familiar with it

Thanks

Jack spoke thusly:
> On Mon, Aug 04, 2008 at 11:54:15AM -0500, David Miller wrote:
> 
> > When I try to combine -u and -/ I get the error:
> > chpst: fatal: unable to get password/group file entry: file does not exist
>  
> I suspect glibc NSS[0] (name service switching). chpst is *probably* trying to
> dlopen() one of the libnss_* files or /etc/nsswitch.conf. I suggest putting
> strace into your chroot, and then tracing chpst. 
> 
> --Jack 
> 
> [0] NSS is also the typical argument the glibc developers use not to support
> static linking. Statically linked binaries are great for chroots, because you
> don't need any libraries. 
> 
> --
> Jack (John) Cummings                           http://mudshark.org/
> PGP fingerprint: F18B 13A3 6D06 D48A 598D  42EA 3D53 BDC8 7917 F802




  reply	other threads:[~2008-08-07  2:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 16:54 David Miller
2008-08-05 14:56 ` Jack Cummings
2008-08-07  2:39   ` David Miller [this message]
2008-08-07  6:23     ` Mike Buland
2008-08-07 20:32       ` David Miller
2008-08-07 20:40         ` Mike Buland
     [not found]         ` <m3abfo7din.fsf@multivac.cwru.edu>
2008-08-07 21:25           ` David Miller
2008-08-07 21:30             ` Mike Buland

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=20080807023941.GA15934@pretender.frop.net \
    --to=dave@frop.net \
    --cc=supervision@list.skarnet.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;
as well as URLs for NNTP newsgroup(s).