[Top][All Lists]

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

Re: [Jailkit-users] Jailkit and Fuse mounted filesystems

From: Richard Scott
Subject: Re: [Jailkit-users] Jailkit and Fuse mounted filesystems
Date: Thu, 13 Dec 2012 16:26:38 +0000
User-agent: Webmail/1.0

ok, I'll give it a try.

I've been trying to make a new RPM with this specfile:  http://endur.fedorapeople.org/downloads/specfiles/jailkit.spec

but get this error at the end:

+ /usr/bin/install -Dp -m0755 /home/makerpm/rpmbuild/SOURCES/jailkit /home/makerpm/rpmbuild/BUILDROOT/jailkit-2.15-2.fc17.x86_64/etc/rc.d/init.d/jailkit
/usr/bin/install: omitting directory `/home/makerpm/rpmbuild/SOURCES/jailkit'
error: Bad exit status from /var/tmp/rpm-tmp.obdg58 (%install)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.obdg58 (%install)

Any ideas on what that could be?




On 13/12/2012 03:18 PM, Olivier Sessink wrote:

On 12/13/2012 01:00 PM, Richard Scott wrote:
Hi, I'm having an issue with using JailKit and fuse mounted filesystem? Specifically GlusterFS: http://www.gluster.org/ I have written a bash script that creates a chroot with jailkit commands and sets the correct permissions etc and this works 100% of the time on an EXT4 FS: 1# Dec 12 15:37:34 recon jk_chrootsh[31029]: now entering jail /home/scott for user richard (1500) with arguments However, when I create a chroot (via the same script) inside the fuse mounted GlusterFS filesystem I get an error: 2# Dec 12 15:43:02 recon jk_chrootsh[31796]: abort, /home/glusterfs/scottg is not a safe chroot jail. In line #1 above I have used the chroot on ext4 and line #2 (the error) is the result from the GlusterFS fuse mounted file system. The same script was used to create both chroots and I am confident that permissions are all ok (as they are set in the script). One thing to note is that it used to work in the past (about 2 years ago). I've rolled back to an older version of GlusterFS and this hasn't fixed it but I've not been able to roll back jailkit due to the symlinks used on Fedora 17. Does anyone have any ideas? Is this a bug?
you can compile jk_chrootsh with more debugging information, enable
#define DEBUG in the top of the file and recompile. This will probably
give a little more information on why it aborts.


reply via email to

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