From: "Sam Roberts" <sam@cogent.ca>
To: "rc" <rc@hawkwind.utcs.toronto.edu>
Subject: Re: rc not session leader?
Date: Fri, 28 Apr 2000 15:03:42 -0400 [thread overview]
Message-ID: <002701bfb144$78ca9ca0$1403a8c0@cogent.ca> (raw)
In-Reply-To: <4.3.1.2.20000428085436.00b3c4e0@mailhost.ocegr.fr>
> >Also, I can't call 'login' from an rc shell, strangely, it
> >complains about not being session leader. I'm quite baffled.
>
> What kind of OS are you using? I can use "login" under solaris and
> freebsd without any problems.
Russ Cox also tells me that login works fine under his system. I
kind of expected that rc was working fine everywhere else.
.............
And in the process of gathering the ps outputs to post here, I
just figured it out. Duh.
login has to be *execed*, not forked/and execed. So login is
a builtin shell alias for "exec login" in QNX's korn shell, so
login gets execed by the shell, the session leader and is happy.
I was trying to run login, so login was being execed by a forked
child of rc, NOT the session leader, and it was failing.
fn login { exec builtin login $* } seems appropriate here...
Thanks!
Sam
next prev parent reply other threads:[~2000-04-28 20:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sroberts@uniserve.com>
2000-04-26 15:02 ` building rc on QNX4 Sam Roberts
2000-04-27 16:56 ` Scott Schwartz
2000-04-27 20:41 ` Sam Roberts
2000-04-28 7:28 ` vrl (was: Re: building rc on QNX4) Gert-Jan Vons
2000-04-28 18:38 ` Sam Roberts
2000-05-02 8:16 ` Gert-Jan Vons
2000-04-28 19:03 ` Sam Roberts [this message]
2000-04-27 17:39 ` building rc on QNX4 Carlo Strozzi
2000-05-02 14:41 ` Tim Goodwin
2000-05-04 15:18 ` Carlo Strozzi
2000-05-08 8:29 ` Tim Goodwin
2000-05-08 8:58 ` Chris Siebenmann
2000-05-08 9:15 ` Tim Goodwin
2000-05-08 23:25 ` Stephen Tell
2000-05-10 0:37 ` builtins Scott Schwartz
2000-05-12 7:22 ` builtins Carlo Strozzi
2000-05-08 11:50 ` building rc on QNX4 David Luyer
2000-05-08 13:28 ` Carlo Strozzi
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='002701bfb144$78ca9ca0$1403a8c0@cogent.ca' \
--to=sam@cogent.ca \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).