PID returns UID for a ps -lx on my Mac Sierra
#11
Comments
ChrisCinelli
changed the title
ps -lx on my Mac Sierra
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Dec 24, 2017
On mac, the ps output can be misaligned, e.g. when some VSZ field is
longer than expected.
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the default fields of ps.
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Dec 25, 2017
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Dec 25, 2017
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Dec 26, 2017
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Dec 29, 2017
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Jan 2, 2018
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Jan 5, 2018
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Jan 10, 2018
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Jan 20, 2018
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Jan 22, 2018
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Mar 17, 2018
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
|
Any chance this is being worked on? |
|
Sorry for spamming the feed with my commits. |
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Jun 6, 2018
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Jun 15, 2018
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Empact
added a commit
to Empact/zap-desktop
that referenced
this issue
Aug 17, 2018
`ps x -o pid,command` rather than `ps lx`
The default ps-node lookup is via ps lx, which includes:
-l Display information associated with the following keywords:
uid, pid, ppid, flags, cpu, pri, nice, vsz=SZ, rss, wchan,
state=S, paddr=ADDR, tty, time, and command=CMD.
On mac, the `ps l` output can be misaligned, e.g. when some VSZ field is
longer than expected.
Many of these fields are unnecessary because we're looking up by name only,
so we can lookup using only the command fields of ps.
https://gist.github.com/ivankovacevic/9918272
More on the issue with ps-node:
neekey/table-parser#11
neekey/ps#64
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using
node-ps. It returns the UID in PID.This is a sample of an output on my
ps lx( I was careful to use the same spacing):The text was updated successfully, but these errors were encountered: