Dariush Pietrzak wrote:
chroot is not a security mechanism, so when you do this, and the tools
you're going to run are compromisied and hostile, then you have just lost
control of your HN and all VE's running on it.
I think, for debugging it could be OK.
tamas
Alexander Prinsier wrote:
Both these make me think that /bin/ls is corrupt. Can you take a
checksum of /bin/ls, and compare it with the /bin/ls of another system
running the same distro?
The corrupt one is smaller.
tamas
___
Users mailing list
Us
Pongracz Istvan wrote:
probably the correct way is:
vzctl exec 100 'strace -ff /bin/ls'
If the strace exists in the container, it must work.
Why shoud I want to run it like this?
I know, it's not working in the container and I want to see it outside.
Thanks,
tamas
__
Alexander Prinsier wrote:
You probably mean "statically linked". /bin/ls usually is dynamically
I'm sorry, of course I mean statically linked.
linked. At least in any standard distro... Statically linked executables
aren't very common.
Well, you are right, I'm confused.
$ ldd /vz/100/pr
Dariush Pietrzak wrote:
$ strace -ff /vz/100/root/bin/ls
You're trying to run a binary from inside the VE in HN's context? I't
dangerous.
And it probably doesn't work because ls is linked to something in VE that
doesn't exist on HN (try ldd /bin/ls or ldd /vz/100/root/bin/ls) (which
would
hi!
$ strace -ff /vz/100/root/bin/ls
execve("/vz/100/root/bin/ls", ["/vz/100/root/bin/ls"], [/* 34 vars */])
= -1 ENOENT (No such file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(3, {st_mode=S_IFCHR|
Roberto Mello wrote:
On Thu, Aug 28, 2008 at 2:57 AM, Papp Tamás <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I mounted a /var partition under /vz/100/root, which should
contain the /var related files.
vzctl start, and I created a test file under it. But
albinootje wrote:
you should use /vz/100/root/ for mounting other things,
not /vz/100/private/
OK, I tried it (I'm sorry for the late answer).
I mounted a /var partition under /vz/100/root, which should contain the
/var related files.
vzctl start, and I created a test file under it. But
hi All,
$ vzctl start 100
Starting VE ...
vzquota : (error) Quota on syscall for 100: Device or resource busy
vzquota on failed [3]
$ umount /vz/100/private/tmp
$ vzctl start 100
Starting VE ...
vzquota : (error) Quota on syscall for 100: Device or resource busy
vzquota on failed [3]
$ umount