From: "Magnus Naeslund\(f\)" <mag@fbab.net>
To: "Marko Kreen" <marko@l-t.ee>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.4 fork() problems (maybe)
Date: Sun, 6 May 2001 02:20:50 +0200 [thread overview]
Message-ID: <018701c0d5c2$67a2ad20$020a0a0a@totalmef> (raw)
In-Reply-To: <00fb01c0d596$afb30690$020a0a0a@totalmef> <20010505223034.C9629@l-t.ee>
From: "Marko Kreen" <marko@l-t.ee>
> On Sat, May 05, 2001 at 09:07:53PM +0200, Magnus Naeslund(f) wrote:
> > Hello, I saw that there was something changed on how fork() works, and
> > wonder if this could be the cause my problem.
> > When i do a "su - <user>" it just hangs.
> > When i run strace on it i see that it forks and wait()s on the child.
> >
> > Sometimes when i strace the su command it succeeds to give me a shell,
> > sometimes not.
> > But it allways fails when i don't strace it.
>
> 2.4.4 has some problems with fork() but your problem seems to be
> something else. Are you using RedHat 7.1? (Or whatever it was
> the latest...) The su-acting-weird problem has been reported
> before and was traced to some PAM problems. Try to download
> some upgrades from RedHat, maybe it will help.
>
> --
> marko
>
No i use redhat 6.2 (on a alpha system).
It works fine with 2.4.3, which i am running now ( i backed out 2.4.4 ).
Magnus
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Programmer/Networker [|] Magnus Naeslund
PGP Key: http://www.genline.nu/mag_pgp.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-05-06 0:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 19:07 2.4.4 fork() problems (maybe) Magnus Naeslund(f)
2001-05-05 19:37 ` Marc Schiffbauer
2001-05-05 20:01 ` J Sloan
2001-05-05 20:05 ` David Lang
2001-05-05 20:30 ` Marko Kreen
2001-05-06 0:20 ` Magnus Naeslund(f) [this message]
2001-05-06 0:39 ` Marko Kreen
2001-05-06 20:11 ` Magnus Naeslund(f)
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='018701c0d5c2$67a2ad20$020a0a0a@totalmef' \
--to=mag@fbab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marko@l-t.ee \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.