Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!sdd.hp.com!cs.utexas.edu!uunet!shaman!jiro
From: jiro@shaman.com (Jiro Nakamura)
Newsgroups: comp.sys.next
Subject: Re: NextStep -> X tranfer problem
Message-ID: <1991Apr29.041036.5734@shaman.com>
Date: 29 Apr 91 04:10:36 GMT
References: <1991Apr29.022737.19106@mp.cs.niu.edu>
Sender: jiro@shaman.com (Jiro Nakamura)
Organization: Shaman Consulting
Lines: 24

In article <1991Apr29.022737.19106@mp.cs.niu.edu> bennett@mp.cs.niu.edu (Scott  
Bennett) writes:
> In article <1991Apr28.203959.13420@cunixf.cc.columbia.edu>  
das15@cunixa.cc.columbia.edu (Douglas A Scott) writes:
> >For times when I need to just kill the entire X apparatus, when it gets  
stuck,
> >I just wrote the following script, which I set to setuid root:
> >
>      The setuid root part shouldn't have any effect, so if it works,
> then you don't need it.  setuid is ignored for shell scripts.

	Sorry Scott, you're wrong on this one. My whole /usr/adm/* directory says  
you're wrong. Setuid is ignored on /bin/sh scripts, I think, but not on  
/bin/csh. 	
	Setuid scripts *are* a security hazard, but they do exist. 

--
Jiro Nakamura				jiro@shaman.com
Shaman Consulting			(607) 253-0687 VOICE
"Bring your dead, dying shamans here!"	(607) 253-7809 FAX/Modem
-- 
Jiro Nakamura				jiro@shaman.com
Shaman Consulting			(607) 253-0687 VOICE
"Bring your dead, dying shamans here!"	(607) 253-7809 FAX/Modem