On Wed, Jul 11, 2001 at 10:56:25AM -0700, larry a price wrote:
> > >And you both need an 'h' for ps or neither will do anything but error out
> > >immediately. kill 'PID' ? slay 'UID' ? Those aren't #'s.
> > >
> > ><[EMAIL PROTECTED]>
> Ah, jake, i don't know about you system but at least under mine it doesn't
> scream to loudly and it goes ahead and does what i expect it
> to. When kill is passed a list of pid's it might complain, but it
> processes the rest of the list before croaking
Actually I just ssh'd to a potato box (probably r1, but as it's only used
by my roommate for Netscape (java/javascript disabled)and to play CDs and
has an uptime of about 100 days, I see no need to update it), and just ran
the ps portion to see what the output would be. Since I don't have any
"lawyers", and I as the only one on the machine (I didn't want to kill
myself, because then I wouldn't see the output), I just figured passing
a bad PID to kill would error and die. That's what happens on OpenBSD
anyway.
% kill 'PID'
kill: illegal pid: PID
% kill 'PID 10101'
kill: illegal pid: PID 10101
% ps -U www -o 'pid'
PID
30526
7138
21427
16130
14875
11189
21367
18681
% sudo kill `ps -U www -o 'pid'`
Password:
kill: illegal process id: PID
% sudo kill `ps -U www -o 'pid' |grep -v PID`
%
BTW, there's no -f, and no h, and -C has a different meaning on BSD
ps.
Is it "A Good Thing", when a command completes even though it is
given a bad argument?
<[EMAIL PROTECTED]>
