[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Jailkit-users] chrootlaunch from inittab

From: DTakemori
Subject: Re: [Jailkit-users] chrootlaunch from inittab
Date: Thu, 19 Mar 2009 09:23:28 -1000

>Date: Tue, 17 Mar 2009 20:58:54 +0100
>From: Olivier Sessink <address@hidden>
>Subject: Re: [Jailkit-users] chrootlaunch from inittab
>To: address@hidden
>Message-ID: <address@hidden>
>Content-Type: text/plain; charset=ISO-8859-1
>address@hidden wrote:

>> I am trying to jail a perl daemon that is launched (and automatically
>> respawned if it dies) from /etc/inittab on a CentOS 5.2 server.
>>The /etc/inittab entry looks something like this:
>>N1:345:respawn:jk_chrootlaunch -u foo -g foo -j /var/foojail -x
>>/usr/local/bin/foo -- -c /usr/local/etc/foo.conf

>> I believe I have initialized the jail correctly because I can run the
>> jailed daemon from
>> the command line as root
>> address@hidden ~ ]# jk_chrootlaunch -u foo -g foo -j /var/foojail -x
>> /usr/local/bin/foo -- -c /usr/local/etc/foo.conf
>> and the daemon runs as expected.
>I guess it runs in the background, right?
>processes that run from inittab must not detach and run in the background.

I should have made it clearer.  No the perl script does not detach, and

in fact it runs just fine from /etc/inittab without the jk_chrootlaunch.
In fact, I am attempting to convert a daemon that was originally setup with
this /etc/inittab entry;

N1:345:respawn:/usr/local/bin/foo -c /usr/local/etc/foo.conf

where /usr/local/bin/foo was owned by foo:foo and had the suid bit set.  To one which is jailed
and does not need the suid bit to run as user/group foo/foo.

Dean Takemori
Systems Support Supervisor
TD Food Group

reply via email to

[Prev in Thread] Current Thread [Next in Thread]