From: Alex <garbanzo@hooked.net>
To: gnu-win32@cygnus.com
Subject: RE: ps, test, /dev/null questions
Date: Fri, 19 Sep 1997 20:10:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.970919200043.1888A-100000@zippy.dyn.ml.org> (raw)
In-Reply-To: <01BCC4E9.E82B7F00@sos>
On Fri, 19 Sep 1997, Sergey Okhapkin wrote:
> Khosla, Deepak wrote:
> > Thanks for all the ideas. I tried a few:
> > - ps -eAf or any other option does not work. I guess as someone
>
> ps command ignores any command line arguments and uses hard-coded output
> format.
>
> > explained, you can only see cygnus processes - not a good port IMHO.
> > Also pview is a grpahical utility AND you have to have the reosurce
> > kit! Anyway, if you have the resource kit, you can use the TLIST
> > command.
>
> NT's built-in task manager will show you all the running processes. Do you
> know a _documented_ way to enumerate running processes on Windows NT?-)
According to the "premium" content on Microsoft's web site
( http://premium.microsoft.com/msdn/library/techart/f365/f36c/f383/d398/sdb7c.htm )
the correct way to get a list of all the processes is to loop through all
the Window handles, and get parent processes too. Seems kludgy to me.
Perhaps a little program is in order to monitor things and make a procfs
like system. Or maybe have an internal method to keep track of programs
linked with cygwin.dll
- alex
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1997-09-19 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-18 23:50 Sergey Okhapkin
1997-09-19 3:22 ` Gunther Ebert
1997-09-19 12:39 ` Lassi A. Tuura
1997-09-19 19:29 ` Hilton Fernandes
1997-09-19 20:10 ` Alex [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-21 12:29 Ken Cantrell
1997-09-18 16:47 Larry Hall
1997-09-19 8:41 ` Pete Jordan
1997-09-18 12:23 Khosla, Deepak
1997-09-20 7:22 ` Michael Hirmke
1997-09-17 11:41 Khosla, Deepak
1997-09-17 21:44 ` Mikey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSF.3.96.970919200043.1888A-100000@zippy.dyn.ml.org \
--to=garbanzo@hooked.net \
--cc=gnu-win32@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).