On Tue, 1 May 2007, [EMAIL PROTECTED] wrote:
> All,
> Thanks for your replies.
>
> > An alternative would be to parse /proc/PID/cmdline.
>
> I think I'll use Tony's solution, as I don't have pstree available on my
> "development" or "live" Cygwin installation. This would be quicker as I can
> use
On Tue, May 01, 2007 at 10:41:19AM +0100, [EMAIL PROTECTED] wrote:
>> An alternative would be to parse /proc/PID/cmdline.
>I think I'll use Tony's solution, as I don't have pstree available on my
>"development" or "live" Cygwin installation. This would be quicker as I can
>use it straight "out of
All,
Thanks for your replies.
> An alternative would be to parse /proc/PID/cmdline.
I think I'll use Tony's solution, as I don't have pstree available on my
"development" or "live" Cygwin installation. This would be quicker as I can
use it straight "out of the box".
I was looking for exactly s
Matthew Woehlke wrote:
Dave Korn wrote:
On 30 April 2007 19:23, Matthew Woehlke wrote:
Anyway, since the information is
available, and most other *nix's 'ps' provides it, any reason Cygwin's
'ps' shouldn't do the same?
I believe you can probably guess the answer to this one...
particularly
Dave Korn wrote:
On 30 April 2007 19:23, Matthew Woehlke wrote:
Dave Korn wrote:
On 30 April 2007 18:48, Matthew Woehlke wrote:
um... and since Cygwin has this information, doesn't this mean that 'ps'
is missing a feature that is standard to pretty much every other *nix
implementation of 'ps
On 30 April 2007 19:23, Matthew Woehlke wrote:
> Dave Korn wrote:
>> On 30 April 2007 18:48, Matthew Woehlke wrote:
>>
>>> um... and since Cygwin has this information, doesn't this mean that 'ps'
>>> is missing a feature that is standard to pretty much every other *nix
>>> implementation of 'ps'?
Dave Korn wrote:
On 30 April 2007 18:48, Matthew Woehlke wrote:
um... and since Cygwin has this information, doesn't this mean that 'ps'
is missing a feature that is standard to pretty much every other *nix
implementation of 'ps'? (I don't have a POSIX standard handy
Yes you do: open brows
On 30 April 2007 18:48, Matthew Woehlke wrote:
> um... and since Cygwin has this information, doesn't this mean that 'ps'
> is missing a feature that is standard to pretty much every other *nix
> implementation of 'ps'? (I don't have a POSIX standard handy
Yes you do: open browser, google "pos
Tony Richardson wrote:
Andy Jet-Net jet-net.co.uk> writes:
In "ps -s" I get something like:
PID TTYSTIME COMMAND
1234 con 09:00:00 /path/program
Is there a way of doing this through ps (or an alternative) in Cygwin?
An alternative would be to parse /proc/PID/cmdline. Arguments are
On Mon, 30 Apr 2007, [EMAIL PROTECTED] wrote:
> Hi all,
>
> I'm trying to get parameters entered at the Cygwin command line to
> appear on my ps command, and failing miserably!
>
> i.e. I'm running the following process at the command line:
>
> program parameter1
>
> In "ps -s" I get something l
Andy Jet-Net jet-net.co.uk> writes:
> In "ps -s" I get something like:
>
> PID TTYSTIME COMMAND
> 1234 con 09:00:00 /path/program
>
> Is there a way of doing this through ps (or an alternative) in Cygwin?
An alternative would be to parse /proc/PID/cmdline. Arguments are
separated by nu
[EMAIL PROTECTED] wrote:
Hi all,
I'm trying to get parameters entered at the Cygwin command line to appear on
my ps command, and failing miserably!
i.e. I'm running the following process at the command line:
program parameter1
In "ps -s" I get something like:
PID TTYSTIME COMMAND
123
On 30 April 2007 12:36, [EMAIL PROTECTED] wrote:
> Hi all,
>
> I'm trying to get parameters entered at the Cygwin command line to appear on
> my ps command, and failing miserably!
> Is there a way of doing this through ps (or an alternative) in Cygwin?
If it doesn't say it in "ps --help" or "
13 matches
Mail list logo
