diff options
author | Ron Yorston <rmy@pobox.com> | 2018-03-28 13:28:03 +0100 |
---|---|---|
committer | Ron Yorston <rmy@pobox.com> | 2018-03-28 13:28:03 +0100 |
commit | 32d2c5ca638aad48233d2b68683a75e905ef9821 (patch) | |
tree | 4083fca2516b30fcd782284e22b561fb18f8203c /TODO | |
parent | 49ef6618c2e101953032b2c660bf7b246d07ce2d (diff) | |
download | busybox-w32-32d2c5ca638aad48233d2b68683a75e905ef9821.tar.gz busybox-w32-32d2c5ca638aad48233d2b68683a75e905ef9821.tar.bz2 busybox-w32-32d2c5ca638aad48233d2b68683a75e905ef9821.zip |
ps: display applet names in process listing
In standalone shell mode all busybox-w32 applets are displayed as
'busybox.exe' in a process listing.
I haven't found a satisfactory way to query a running instance of
busybox-w32 to determine which applet it's running. Handle a couple
of cases:
- the process running the process scan knows its own PID and knows
which applet it is;
- just before invoking applet_main set an environment variable whose
name contains the PID and whose value is the current applet name.
Children running a process scan will inherit their parent's environment
and can therefore match the parent's PID to its applet name.
Diffstat (limited to 'TODO')
0 files changed, 0 insertions, 0 deletions