From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: PS and AWK Linux Commands on Cygwin
Date: Thu, 04 Aug 2016 13:55:00 -0000 [thread overview]
Message-ID: <959134cd-434f-f51a-0c0b-bba7a285356a@cs.umass.edu> (raw)
In-Reply-To: <742cdb45-d345-5d5d-2c59-f31c4a2f243a@winfirst.com>
On 8/4/2016 9:20 AM, Mark Hansen wrote:
> On 8/4/2016 6:12 AM, Eliot Moss wrote:
>> So, a couple of things ...
>>
>> Cygwin definitely supports gawk - I use it all the time.
>> My system has a link from awk to gawk, so awk will work.
>> I can't recall if I added that link or if it came with
>> the installation. awk may be in a separate package
>> that you'll have to install from the Cygwin package
>> installer.
>
> I have a fresh installation of Cygwin and /usr/bin/awk is a link to /usr/bin/gawk - FYI
>
>>
>> As for ps, it works, but it will show only Cygwin
>> related processes. It may have other limitations
>> as well, because it might be impossible or very
>> difficult to support some POSIX features under
>> Windows.
>
> Cygwin ps allows for a -W command-line argument which tells it to include all windows processes.
> There are other arguments like -l for "long" mode, -f for "full" mode, etc.
Thanks for the additional info!
On Windows, procps is useful, but of course it's Windows-specific ...
Regards - EM
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-08-04 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1278249779.9195574.1470314208273.JavaMail.yahoo.ref@mail.yahoo.com>
2016-08-04 13:12 ` Scott Geiger
2016-08-04 13:23 ` Eliot Moss
2016-08-04 13:30 ` Mark Hansen
2016-08-04 13:55 ` Eliot Moss [this message]
2016-08-04 14:35 ` Scott Geiger
2016-08-04 18:31 ` Andrey Repin
2016-08-05 9:31 ` Mark Hansen
2016-08-05 14:57 ` cyg Simple
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=959134cd-434f-f51a-0c0b-bba7a285356a@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.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).