First, I'm not sure that simply settings argv[0]
in a C program portably changes the name shown in ps
. Maybe it does in some unixen, but my understanding is that it's not expected to.
Second, since Windows is specifically non-POSIX compliant, only a few things are "portable" between POSIX and non-POSIX. Since you specifically say 'ps', I'll assume that POSIX is your priority and Windows may not work.
More importantly, my understanding of changing argv[0]
is that it requires a call to exec
to make these changes. Specifically, the exec
call has both a path to an executable and a separate argv
list. Making your own call allows you to break the shell convention of putting the executable name in argv[0]
.
You have OS library process management which gives you direct access to the OS library for doing this. You should consider breaking your script into two parts -- a starter and the "real work". The starter establishes the run-time environment and exec's the real work with the desired parameters.
In C, you're replacing your own process with another. In Python, you're replacing the old Python interpreter with a new one that has a different argv[0]. Hopefully, it won't balk at this. Some programs check argv[0] to decide what they're doing.
You also have subprocess.popen that you can use to set your desired args and executable. In this case, however, the parent process should lingers around to collect the child when the child finishes. The parent may not be doing anything more than a Popen.wait