Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!think!mintaka!ogicse!zephyr.ens.tek.com!uw-beaver!ubc-cs!alberta!dvinci!news
From: lowey@herald.usask.ca (Kevin Lowey)
Newsgroups: comp.os.os2
Subject: Re: Security concerns for OS/2?
Message-ID: <1990Mar24.000952.11216@dvinci.usask.ca>
Date: 24 Mar 90 00:09:52 GMT
References: <28153@ubvax.UB.Com>
Sender: news@dvinci.usask.ca
Reply-To: lowey@herald.usask.ca
Organization: University of Saskatchewan
Lines: 14

From article <28153@ubvax.UB.Com>, by scott@ubvax.UB.Com (Scott Scheiman):
>>virus process can do its work in the background, but os/2 has a real
>>process model which the virus would have to be using, and a real
>>process list command for you to see that virus at work - this would, of

> Um, what is that "list command"?  If you are talking about an API entry,
> then it isn't useful to anybody unless some application is built around
> it.

I'm not sure if this is what he means, but OS/2 1.2 has a command called 
PSTAT which shows the current status of all the processes, threads, etc.
running in the system.

-- Kevin Lowey