Peter O'Gorman wrote:
[]
>
> I imagine that it will be closed as invalid. With -a, you are
> essentially asking for all processes with a controlling terminal, with
> -p you ask for all processes which match the given process id. ps will
> return both all the processes with a controlling terminal a
Martin Costabel wrote:
>
> Good catch. To me this looks like a bug in Leopard's /bin/ps: When the
> "-a" flag is present, it ignores the "-p pid" flag. I have immediately
> filed a bug with Apple's bugreporter.
I imagine that it will be closed as invalid. With -a, you are
essentially asking fo
Martin Costabel wrote:
> Good catch. To me this looks like a bug in Leopard's /bin/ps: When the
> "-a" flag is present, it ignores the "-p pid" flag. I have immediately
> filed a bug with Apple's bugreporter.
>
> The environment variables (in particular $HOME and $USER) with which the
> insta
Evan Broder wrote:
> Hi,
> I think I've got a patch that fixes the postflight script on 10.5.
>
> There are two things that I fix: first, ps axww seems to for some reason
> list lots of processes on 10.5. I will freely admit that I don't
> understand the options to ps on OS X or any other pl
(Sorry - this is in the scripts module if that's not clear)
- Evan
Evan Broder wrote:
> Hi,
> I think I've got a patch that fixes the postflight script on 10.5.
>
> There are two things that I fix: first, ps axww seems to for some reason
> list lots of processes on 10.5. I will freely admit
Hi,
I think I've got a patch that fixes the postflight script on 10.5.
There are two things that I fix: first, ps axww seems to for some reason
list lots of processes on 10.5. I will freely admit that I don't
understand the options to ps on OS X or any other platform - I just kept
pulling a