Killing process w/o number (csh)

Scott P Nichols nichols at en.ecn.purdue.edu
Fri Apr 26 09:53:04 AEST 1991


In article <153231 at pyramid.pyramid.com> moliver at shadow.pyramid.com (Mike Oliver) writes:
>In article <1991Apr24.214750.24522 at athena.mit.edu> jik at athena.mit.edu (Jonathan I. Kamens) writes:
>>In article <+-A_7A#@warwick.ac.uk>, cudcv at warwick.ac.uk (Rob McMahon) writes:
>>|> I've always wondered why people always do this rather than
>>|> 
>>|> 	ps axc | grep sysline
>>
>>Because the 'c' option to grep isn't universally supported.
>
>That's what I said in e-mail, but Rob pointed out that the original use
>of `ps -ax' probably means that this is a BSD system which will also
>understand the `-c' option.
>
>The giveaway is that the AT&T `ps' doesn't support `-x'.  (Of course,
>it's always possible that there's some weird variant of a `ps' out
>there that accepts `-ax' and doesn't accept `-axc'.  I don't know of
>one.)
>
>As an aside - if you're on an AT&T system, `ps -e' produces something
>that looks a lot like the Berkeley `ps -axc'.
>
>Cheers, Mike.

As the original asker of the question, I will confirm that ps -x did
what I wanted.  If I type ps -ax, I get the processes for all users,
not just me.  I don't think the -a is necessary.

Thanks for all of your advice.

Scott
-- 
O-        /\
|\     /\/vv\                  _Insight from Oregon...Scott P. Nichols
      /vv\   \        	      /                     (nichols at en.ecn.purdue.edu)
_____/    \   ~~~~~~~~~~~~~~~~                         (nichols at techbook.com)



More information about the Comp.unix.shell mailing list