home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!ames!agate!agate!robm
- From: robm@ataraxia.Berkeley.EDU (Rob McNicholas)
- Newsgroups: comp.unix.ultrix
- Subject: Re: :permission denied?
- Date: 8 Sep 92 12:12:25
- Organization: Technical and Computing Services, U.C. Berkeley, Berkeley, CA
- Lines: 27
- Message-ID: <ROBM.92Sep8121225@ataraxia.Berkeley.EDU>
- References: <1992Sep3.073220.1@vax.sonoma.edu> <1992Sep3.151848.23143@decuac.dec.com>
- <1354@niktow.canisius.edu>
- NNTP-Posting-Host: ataraxia.berkeley.edu
- In-reply-to: pavlov@niktow.canisius.edu's message of 8 Sep 92 03:13:22 GMT
-
- In article <1354@niktow.canisius.edu> pavlov@niktow.canisius.edu (Greg Pavlov) writes:
- We encounter something similar using su (legitimately...). The
- command does what it is supposed to, but we typically get the
- following message:
-
- /dev/ttyp2: permission denied
-
-
-
- When you rlogin to a system, you become the owner of the pty you've
- connected through. If you su to someone who doesn't have permission
- to write to your pty (usually anyone other than root), and they have
- some line in their .cshrc file which is attempting to modify the pty
- (for example, an stty, biff, or mesg command), that command will fail
- with the "permission denied" message.
-
- "su -f user" should avoid this.
-
- Another thing to watch out for is su'ing to someone who doesn't have
- search permission to the current directory. Then you get
- "getwd: Permission denied -- can't start new shell"
-
- -Rob
-
- --
- Rob McNicholas Technical & Computing Services, EECS, U.C. Berkeley
- robm@ataraxia.berkeley.edu Voice: 510/642-8633 FAX: 510/643-7846
-