Path: utzoo!attcan!uunet!mcsun!hp4nl!tuegate.tue.nl!eba!wjw
From: wjw@eb.ele.tue.nl (Willem Jan Withagen)
Newsgroups: comp.sys.apollo
Subject: Re: /etc/killall, what is it?
Keywords: undocumented, dangerous, /etc/killall
Message-ID: <560@eba.eb.ele.tue.nl>
Date: 30 Jul 90 12:24:12 GMT
References: <551@eba.eb.ele.tue.nl> <1990Jul28.142626.28237@IRO.UMontreal.CA> <1990Jul28.204241.14946@terminator.cc.umich.edu>
Sender: wjw@eba.eb.ele.tue.nl (Willem Jan Withagen)
Reply-To: wjw@eb.ele.tue.nl
Followup-To: comp.sys.apollo
Organization: Eindhoven University of Technology, The Netherlands
Lines: 36

>In article <1990Jul28.142626.28237@IRO.UMontreal.CA>,
>goutier@IRO.UMontreal.CA (Claude Goutier) writes:
>
>I don't consider killall to be dangerous to the system, since it doesn't let
>you kill any process you don't own.  It may be dangerous to individual users,
>but anyone who runs a program named "killall" without first finding out what
>it does deserves whatever they get.
>
I agree to the above statement,

BUT it does harm programs which are not owned by the user!!!!!!

Running 'killall' kills the service-process-manager. It runs under the
user: "user.server.none" and is aborted by killall.

Now the 'spm' is not a real vital program, and it does not crash the node
but it is very anoing when user complain that they can't 'crp'
because somebody else killed the spm!

And what about: "Can only be run by the SUPER-USER"!

Since I now know that it belongs to Sys5, I'm going to delete it.
(We don't run Sys5 any longer)
So it solves my problem, but all those outthere running Sys5 should
change the settings to something like rwx------ root wheel /etc/killall
to fullfil the manual's requirement.

Regards,

	Willem Jan Withagen               

Eindhoven University of Technology   DomainName:  wjw@eb.ele.tue.nl    
Digital Systems Group, Room EH 10.10 BITNET: ELEBWJ@HEITUE5.BITNET
P.O. 513                             Tel: +31-40-473401
5600 MB Eindhoven                 
The Netherlands