diff options
| author | Ron Yorston <rmy@pobox.com> | 2023-08-29 14:55:24 +0100 |
|---|---|---|
| committer | Ron Yorston <rmy@pobox.com> | 2023-08-29 15:11:14 +0100 |
| commit | 89e67c6f7a77e0e16cbf394f18d4cb121e37f544 (patch) | |
| tree | c286c985453ff263dc6d84774e18b298399e35e5 /runit | |
| parent | d6fb7a2c36f8a6d5fac4754cdfdb5483a03f2892 (diff) | |
| download | busybox-w32-89e67c6f7a77e0e16cbf394f18d4cb121e37f544.tar.gz busybox-w32-89e67c6f7a77e0e16cbf394f18d4cb121e37f544.tar.bz2 busybox-w32-89e67c6f7a77e0e16cbf394f18d4cb121e37f544.zip | |
ps: increase length of 'comm' field
In Linux the command name associated with a process (as can be
obtained from '/proc/<PID>/comm') is truncated to 16 characters.
Thus upstream BusyBox only allows 16 characters for the 'comm'
field in 'ps'.
There's no need for such a constraint in busybox-w32. Moreover,
the command name is used for the full command line ('args' field)
in most cases. This field is allowed to be rather long in 'ps'
so it's not expected to be truncated.
Still, to avoid diverging too much from upstream it's best to have
some measure of truncation. Increase the allowed length of the
command name to 32 characters.
Adds 16 bytes.
(GitHub issue #358)
Diffstat (limited to 'runit')
0 files changed, 0 insertions, 0 deletions