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,
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
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
Pongracz Istvan wrote:
2008. 12. 4, csütörtök keltezéssel 12.01-kor Alexander Prinsier ezt
írta:
Papp Tamás wrote:
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
Vasily Averin wrote:
btw
you can mount container by 'vzctl mount 100' command,
then you can make chroot /vz/root/100
and then start strace
Is it a big mistake to chroot only to /vz/private/100 without vzctl mount?
tamas
___
Users mailing list
Papp,
I don't think you have stated what distro you are running in the problem
container. Most package managers offered by distros have a way to verify the
checksums of packages installed by the package manager. So enter the container
and do that. The modified files should stick out like a
