New builded packages do not show up with their name as command with ps/pgrep/pkill , /proc about vsc-install HOT 8 OPEN

[root@osd010 ~]# cat /proc/2302819/cmdline
/usr/bin/python-E/usr/bin/zkrsync--configfiles=/etc/zkrs/kyukonhome.conf--session=kyukonhome--daemon-D

still shows /usr/bin/zkrsync in there

from vsc-install.

@JensTimmerman osd010 wasn't updated yet

from vsc-install.

same on osd009

[root@osd009 ~]#  cat /proc/2278866/cmdline
/usr/bin/python-E/usr/bin/zkrsync--configfiles=/etc/zkrs/kyukonhome.conf--session=kyukonhome--daemon-D

from vsc-install.

@JensTimmerman try ps -C
i guess the new wrapper in the shebang does an exec and ps sometimes shows before vs after exec?

from vsc-install.

@stdweird I know the procname is different, that is indeed changed, just trying to give some alternatives here.

If you consider this a bug, we could have the wrapper set the correct procname (linux only) with

def set_proc_name(newname):
    from ctypes import cdll, byref, create_string_buffer
    libc = cdll.LoadLibrary('libc.so.6')
    buff = create_string_buffer(len(newname)+1)
    buff.value = newname
    libc.prctl(15, byref(buff), 0, 0, 0)

but this seems a bit hacky

from vsc-install.

@JensTimmerman oh, i don't consider it a bug 😄
it would be nice to understand why it happened, but nothing more then that imho.
@kwaegema your fixes in https://github.ugent.be/hpcugent/vsc-backup/pull/6 are sufficient to work around this, right?

from vsc-install.

It happens because we now always call python, via
https://github.com/hpcugent/vsc-install/blob/master/bin/python-stripped-env#L32

maybe we should exec it instead?

from vsc-install.

@JensTimmerman ah, we wrote that. what happens if you use exec $PYTHON ... to start it?

from vsc-install.