Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sgi!archer@elysium.SGI.COM
From: archer@elysium.SGI.COM (Archer Sully)
Newsgroups: comp.sys.sgi
Subject: Re: SGI 'su'
Summary: It works fine
Message-ID: <28714@sgi.SGI.COM>
Date: 15 Mar 89 17:50:31 GMT
References: <8903141821.AA07266@adt.uucp>
Sender: daemon@sgi.SGI.COM
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 17

In article <8903141821.AA07266@adt.uucp>, madd@adt.UUCP (jim frost) writes:
> I would appreciate it very, very much if someone would fix 'su' so it
> properly reads the destination user's shell configuration files.  I'm
> about to hack one together but I really shouldn't have to do that.
> 
> This is very important to me since our root .cshrc properly sets the
> prompt to the hash mark, but this is never called when su'ing.  If you
> forget, or if someone walks up, you or they will unknowingly be root.
> This is of course very dangerous even if security isn't an issue.

This is normal, proper System V behavior for su.  If you use 'su -', then
the full login procedure is followed.  If you don't wish to use su - for 
whatever reason, you can have your own .cshrc check your uid, and set
the prompt to a # when you are root.

archer
--