Re: [Jailkit-users] jk_chrootlaunch processes staying around?

[Olivier Sessink]

Gregory Piñero wrote:
> I'm getting some odd behavior from jk_chrootlaunch.
> 
> The basic idea is I have a program run as root that runs this command
> four times:
> jk_chrootlaunch -u jaileduser -g jaileduser -j /srv/jail_dir/ --exec
> /usr/bin/python2.5 exec_worker.py
> 
> It should leave 4 instances of exec_worker.py running from the
> jaileduser in the jail.
> 
> However when I run ps aux | grep python
> 
> I get this:
> 
> root      2195  0.0  0.1   1712   480 ?        S    00:33   0:00
> /bin/sh -c jk_chrootlaunch -u jaileduser -g jaileduser -j
> /srv/jail_dir/ --exec /usr/bin/python2.5 exec_worker.py
> 1001      2196  0.6  1.4   6764  4356 ?        S    00:33   0:00
> /usr/bin/python2.5 exec_worker.py
> root      2197  0.0  0.1   1712   480 ?        S    00:33   0:00
> /bin/sh -c jk_chrootlaunch -u jaileduser -g jaileduser -j
> /srv/jail_dir/ --exec /usr/bin/python2.5 exec_worker.py
> 1001      2198  0.7  1.4   6776  4364 ?        S    00:33   0:00
> /usr/bin/python2.5 exec_worker.py
> root      2199  0.0  0.1   1716   484 ?        S    00:33   0:00
> /bin/sh -c jk_chrootlaunch -u jaileduser -g jaileduser -j
> /srv/jail_dir/ --exec /usr/bin/python2.5 exec_worker.py
> 1001      2200  0.5  1.4   6768  4360 ?        S    00:33   0:00
> /usr/bin/python2.5 exec_worker.py
> root      2201  0.0  0.1   1716   480 ?        S    00:33   0:00
> /bin/sh -c jk_chrootlaunch -u jaileduser -g jaileduser -j
> /srv/jail_dir/ --exec /usr/bin/python2.5 exec_worker.py
> 1001      2202  0.2  1.4   6764  4356 ?        S    00:33   0:00
> /usr/bin/python2.5 exec_worker.py
> 
> So my questions are:
> 
> 1. Why are these root process sticking around?

it's the /bin/sh process sticking around, not the jk_chrootlaunch. So I
don't know how you start these 4 processes, but I guess it's some
script, and this script is the reason you see 4 /bin/sh processes.

> 2. Why does 1001 appear instead of jaileduser?

I have no clue. 1001 is 'jaileduser' ?

Olivier