Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site bu-cs.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!bu-cs!root
From: root@bu-cs.UUCP (Barry Shein)
Newsgroups: net.unix-wizards
Subject: Re: Strange behavior of su
Message-ID: <667@bu-cs.UUCP>
Date: Sun, 22-Sep-85 16:50:20 EDT
Article-I.D.: bu-cs.667
Posted: Sun Sep 22 16:50:20 1985
Date-Received: Wed, 25-Sep-85 09:40:56 EDT
References: <314@aphasia.UUCP>, <323@uwvax.UUCP>
Organization: Boston Univ Comp. Sci.
Lines: 28

From: dave@uwvax.UUCP (Dave Cohrs)
>> Every now and then after I have been logged in for a while I will try to
>> su, have su ask the password, and then it sits for a bit and exits.  It
>> does not generate any error messages, the exit status is 0.  After this
>> has happened it will keep happening until I log out, I have always been
>> able to su immediately after logging in.
>
>You didn't say to whom you were su'ing.  However, if you were becoming
>root, this behaviour doesn't make sense.  If you were becoming another
>normal user, this probably means the current directory was inaccesable
>to the new user.  In this case, su gives up quietly.  I think this is
>a case there things could be a bit more verbose.

You better explain which version of UNIX you believe this happens
(su exits silently if '.' is not accessible.)

I just tried it under 4.2bsd (vax), SYSVR2 (3b5) and SYSVR(1?) (PC7300)
and all let me su to a non-priv'd user while in a directory they had
no access to, of course:

	% ls
	. not found
	%

was the amusing side effect, but that is not what you said (and that is
a non-fatal and correct side-effect and has nothing to do with su.)

	-Barry Shein, Boston University


Brought to you by Super Global Mega Corp .com