linking to libc and libc_r (was Re: Certain 4.10 apps failing to run as root)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here's an update... On Thu, 10 Jun 2004 09:12:33 -0600 Anthony Chavez <[EMAIL PROTECTED]> wrote: > I think that Kris has been swallowed up by other efforts at the moment, > so I'm moving this to the freebsd-stable list, where it's probably more > rele

Re: Certain 4.10 apps failing to run as root

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think that Kris has been swallowed up by other efforts at the moment, so I'm moving this to the freebsd-stable list, where it's probably more relevant anyhow. On Thu, 03 Jun 2004 01:35:33 -0600 Anthony Chavez <[EMAIL PROTECTED]> wrote: > I just upgr

Re: Certain 4.10 apps failing to run as root

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 3 Jun 2004 01:27:57 -0700 Kris Kennaway <[EMAIL PROTECTED]> wrote: > I've only seen this when something incorrectly links to both libc and > libc_r. Neither of those four binaries should be linked to libc_r at > all though. Can you confirm wi

Re: Certain 4.10 apps failing to run as root

On Thu, Jun 03, 2004 at 01:35:33AM -0600, Anthony Chavez wrote: > I just upgraded one of my machines to 4.10-STABLE from 4.9-STABLE and > certain binaries (such as vim or vipw) when run as root (either with > sudo or su -) freeze up with "rcmdsh: unknown user:" followed by a bunch > of garbage. I'

Certain 4.10 apps failing to run as root

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just upgraded one of my machines to 4.10-STABLE from 4.9-STABLE and certain binaries (such as vim or vipw) when run as root (either with sudo or su -) freeze up with "rcmdsh: unknown user:" followed by a bunch of garbage. I seem to remember encounte