[Pkg-virtualbox-devel] Bug#802143: virtualbox-ext-pack: doesn't use invoke-rc.d - leaves processes running after purge

[Andreas Beckmann]

On 2016-01-13 12:52, Gianfranco Costamagna wrote:
> well, do you know about a real use case where procps is not available?
> even pbuilder installs it by default, and apt tells me to "yes, do what I say" answer
> when I try to remove it.

There is no procps in the ultra-minimal chroots used by piuparts :-)
I have procps in my pbuilder chroot, too, but mainly because *my*
metapackage depends on it. But I had no problems removing it (after my
metapackage).

> I can add it as runtime dependency if needed, sure!
> 
> probably it is done to kill some processes if they don't exit in 5 seconds.
> 
> let me know if I have to add it (on virtualbox, not in ext-pack)

The code that uses it (from /usr/bin/vboxmanage) is

SERVER_PID=`ps -U \`whoami\` | grep VBoxSVC | awk '{ print $1 }'`
if [ -z "$SERVER_PID" ]; then
    # Server not running yet/anymore, cleanup socket path.
    # See IPC_GetDefaultSocketPath()!
    if [ -n "$LOGNAME" ]; then
        rm -rf /tmp/.vbox-$LOGNAME-ipc > /dev/null 2>&1
    else
        rm -rf /tmp/.vbox-$USER-ipc > /dev/null 2>&1
    fi
fi

So it removes the socket path unconditionally because SERVER_PID is
always empty due to missing ps. But if vbox is usually run as a normal
user, there shouldn't be any VBoxSVC processes running as root, or am I
mistaken here?


Andreas

PS: looks like I cannot reproduce the leftover process problem any more
while testing the latest version of virtualbox(-ext-pack) with piuparts
(without doing any changes on my side)