fixed in cvs. A typo in the argument
parsing. Nothing serious, but very inconvenient.
Olivier
On 04/25/2013 04:22 PM, Richard Scott wrote:
Hi,
I've upgraded my RPM's to 2.16 using the .spec file in the
tarball and everything looked ok...
When it comes to using the jk_cp command I get unexpected
problems.
I created my chroot with this command:
address@hidden ~]# jk_init -j
/opt/chroot terminfo ssh sftp scp
and everything works ok.
I then try and copy bash over to the chroot and I get issues:
address@hidden ~]#jk_cp -j
/opt/chroot /bin/bash
ERROR: is not a directory
Usage: /sbin/jk_cp -j <jail> [OPTIONS] <files
and directories>
-h --help : this help screen
-j, --jail : the jail to copy to
-v, --verbose : show what is being copied
-f, --force : overwrite existing files
-k, --hardlink : use hardlinks if possible
-o, --owner : retain file ownership and group
-s, --setuid : retain file setuid/setgid bits
Note: if no jail is specified, the first argument is
considered to be the jail
However, if I omit the "-j" from the command line, all seems to
work:
address@hidden ~]# jk_cp
/opt/chroot /bin/bash
usr/bin /opt/chroot/bin
Copying /bin/bash to /opt/chroot/usr/bin/bash
Creating symlink /opt/chroot/usr/lib64/libtinfo.so.5 to
libtinfo.so.5.9
Copying /lib64/libtinfo.so.5.9 to
/opt/chroot/usr/lib64/libtinfo.so.5.9
am I doing something stupid or has the usage of "-j" changed?
Thanks,
Rich
_______________________________________________
Jailkit-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/jailkit-users