Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site psivax.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!psivax!friesen
From: friesen@psivax.UUCP (Stanley Friesen)
Newsgroups: net.unix-wizards
Subject: Re: Strange behavior of su
Message-ID: <744@psivax.UUCP>
Date: Mon, 23-Sep-85 13:15:44 EDT
Article-I.D.: psivax.744
Posted: Mon Sep 23 13:15:44 1985
Date-Received: Sat, 28-Sep-85 05:11:14 EDT
References: <314@aphasia.UUCP>
Reply-To: friesen@psivax.UUCP (Stanley Friesen)
Distribution: net
Organization: Pacesetter Systems Inc., Sylmar, CA
Lines: 27

In article <314@aphasia.UUCP> gww@aphasia.UUCP (George Williams) writes:
>We are running bsd4.2 on a vax 750.
>
>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.
>
	Well, since at least two people have asked, I will make this a
Followup instead of a Reply.
	I too have had this problem, and it seems to occur when the
user specified to 'su' does not have r and x permissions to all
directories between / and the current working directory. All you need
to do to get around it is to cd to a directory with general r & x
permissions with the same permissions for all parent directories.
(Apparently the problem is that the *shell* will exit if it cannot
access the current directory, & since su thinks it has executed the
shell correctly it gives no error message.)
	P.S this also explains why this never happens when you su to
root, since root has universal access.
-- 

				Sarima (Stanley Friesen)

UUCP: {ttidca|ihnp4|sdcrdcf|quad1|nrcvax|bellcore|logico}!psivax!friesen
ARPA: ttidca!psivax!friesen@rand-unix.arpa


Brought to you by Super Global Mega Corp .com