Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site amdahl.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!crsp!pesnta!amdcad!amdahl!gam
From: gam@amdahl.UUCP (gam)
Newsgroups: net.unix-wizards
Subject: re: ps problem
Message-ID: <1079@amdahl.UUCP>
Date: Sat, 2-Feb-85 01:09:24 EST
Article-I.D.: amdahl.1079
Posted: Sat Feb  2 01:09:24 1985
Date-Received: Sat, 2-Feb-85 15:05:24 EST
References: <125@rruxo.UUCP>
Organization: Blue Mouse Trailer Resort, Hellmouth, CA
Lines: 17

> Ah, finally one I know.
> nohup-ing ps losses the user information and therefore doesn't
> print processes for you.  If you try nohup ps -u[your login], it will work!

It probably will, but not because of lost user information.  It is
because ps(1) looks at stderr to figure out what the "controlling
terminal" is; nohup redirects stderr to nohup.out, thus there is
no "controlling terminal."  It also does not handle this case
correctly, as it blithely assumes stderr is ALWAYS a terminal.

Your example gives different selection criteria (user id) and thus
works; the default is to select all processes associated with the
current terminal.

(this was a fun problem!).
-- 
Gordon A. Moffett		...!{ihnp4,hplabs,sun}!amdahl!gam