Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84 exptools; site ho95e.UUCP Path: utzoo!linus!philabs!cmcl2!harvard!seismo!lll-crg!dual!qantel!ihnp4!houxm!ho95e!wcs From: wcs@ho95e.UUCP (Bill.Stewart.4K435.x0705) Newsgroups: net.bugs.usg Subject: Re: Not Necessarily a Bug (but worth reading) Message-ID: <189@ho95e.UUCP> Date: Tue, 24-Sep-85 13:41:58 EDT Article-I.D.: ho95e.189 Posted: Tue Sep 24 13:41:58 1985 Date-Received: Tue, 1-Oct-85 08:07:11 EDT References: <668@bu-cs.UUCP> Organization: AT&T Bell Labs, Holmdel NJ Lines: 17 Keywords: Restricted shells, SVR2 /bin/sh buggy, ksh works fine > A gotcha in the shell that almost caused me further permanent brain-damage: > > Not Necessarily a Description: > > /bin/sh in SYSVR2 will look for the character 'r' *anywhere* in it's > argv[0] when it starts up and, upon finding one, will run in restricted > mode. > ............... > -Barry Shein, Boston University Hmmm.. it does seem to do that on my 3B20. $ cp /bin/sh braindamage $ braindamage $ >junk junk: restricted So I tried it with ksh (the Korn Shell), and I didn't have this problem. -- ## Bill Stewart, AT&T Bell Labs, Holmdel NJ 1-201-949-0705 ihnp4!ho95c!wcs