list its instances.
I was thinking about using procps or printing /proc/*/cmdline.
However, some of the users do not have admin rights, so they are not allowed
to access /proc/pid/cmdline, /proc/pid/stat etc... of other users...
This is why ps -ef giving command line arguments would be really
On Mon, May 20, 2013 at 10:32:07AM +0200, AZ 9901 wrote:
Do you think ps command could be corrected / improved to display
myscript (script's name according to the example above) and/or
command line arguments ?
We have no plans on modifying Cygwin's ps program.
--
Problem reports:
of the users do not have admin rights, so they are not allowed to
access /proc/pid/cmdline, /proc/pid/stat etc... of other users...
This is why ps -ef giving command line arguments would be really perfect !
But perhaps there is another solution ?
Could you help me ?
Thank you very much,
Best
procps or printing /proc/*/cmdline.
However, some of the users do not have admin rights, so they are not allowed
to access /proc/pid/cmdline, /proc/pid/stat etc... of other users...
This is why ps -ef giving command line arguments would be really perfect !
I also just tested a workaround
On 5/7/2013 02:46, AZ 9901 wrote:
This script uses ps -ef in particular to list all its instances.
Any script that relies on 'ps' output parsing is probably unportable
from the get-go.
Your script will also fail on most FreeBSD machines, for example. On
FreeBSD, there is a kernel build
Le 7 mai 2013 à 16:39, Warren Young a écrit :
Your script will also fail on most FreeBSD machines, for example. On
FreeBSD, there is a kernel build option that is often set which prevents user
space from *ever* seeing command line options. It's a security feature,
since there are all
6 matches
Mail list logo
