Either we can overwrite argv[0], or prctl (PR_SET_MM_ARG_START, PR_SET_MM_ARG_END – the preferred way). We can do this via a NIF.

does `prctl (PR_SET_MM_ARG_START, PR_SET_MM_ARG_END – the preferred way).` override the memory that argv points to?

systemd can help us. In ExecStart=

For each of the specified commands, the first argument must be an absolute path to an executable. Optionally, if this file name is prefixed with "@", the second token will be passed as "argv[0]" to the executed process, followed by the further arguments specified. If the absolute filename is prefixed with "", an exit code of the command normally considered a failure (i.e. non-zero exit status or abnormal exit due to signal) is ignored and considered success. If both "" and "@" are used, they can appear in either order.

From Erlang 20.0-rc1 release notes:

OTP-14381 Application(s): erts

Changed erts startup program name, argv 0, to use the
environment variable ESCRIPT_NAME so that erlc,
dialyzer, typer, ct_run, or the escript name can be
seen with external programs, such as ps and htop
(depending on options), on unix.

If environment variable ESCRIPT_NAME is not set, argv 0
of the invoking program will be used, e.g. the name
will be erl, cerl, or the soft link name.

I've made it as part of https://jira.mesosphere.com/browse/DCOS_OSS-1400