[Vserver] setattr - Bad address

2005-04-04 Thread Michal Ludvig
Hi all, I'm trying to set up vserver on my SuSE Linux 9.2 box running 2.6.11.5 kernel with vserver 1.9.5 patch and util-vserver-0.30.204. I met a number of issues, perhaps because this is the first time I play with vservers. 1) vprocunhide (i.e. setattr) spits out a lot of Bad address messages.

Re: [Vserver] setattr - Bad address

2005-04-04 Thread Bjoern Steinbrink
On 2005.04.05 12:41:12 +1200, Michal Ludvig wrote: Hi all, I'm trying to set up vserver on my SuSE Linux 9.2 box running 2.6.11.5 kernel with vserver 1.9.5 patch and util-vserver-0.30.204. I met a number of issues, perhaps because this is the first time I play with vservers. 1)

Re: [Vserver] setattr - Bad address

2005-04-04 Thread Herbert Poetzl
On Tue, Apr 05, 2005 at 12:41:12PM +1200, Michal Ludvig wrote: Hi all, I'm trying to set up vserver on my SuSE Linux 9.2 box running 2.6.11.5 kernel with vserver 1.9.5 patch and util-vserver-0.30.204. I met a number of issues, perhaps because this is the first time I play with vservers.

Re: [Vserver] setattr - Bad address

2005-04-04 Thread Michal Ludvig
Herbert Poetzl wrote: On Tue, Apr 05, 2005 at 12:41:12PM +1200, Michal Ludvig wrote: puck:root:~# /usr/local/sbin/setattr /proc/uptime /proc/uptime: Bad address that is at least unusual ... you sure the kernel was compiled with the vserver patch? Yes, it is. But the binary is somehow

Re: [Vserver] setattr - Bad address

2005-04-04 Thread Herbert Poetzl
On Tue, Apr 05, 2005 at 01:32:59PM +1200, Michal Ludvig wrote: Herbert Poetzl wrote: On Tue, Apr 05, 2005 at 12:41:12PM +1200, Michal Ludvig wrote: puck:root:~# /usr/local/sbin/setattr /proc/uptime /proc/uptime: Bad address that is at least unusual ... you sure the kernel was

Re: [Vserver] setattr - Bad address

2005-04-04 Thread Michal Ludvig
Herbert Poetzl wrote: On Tue, Apr 05, 2005 at 01:32:59PM +1200, Michal Ludvig wrote: I'm now recompiling without optimalizations and with debug symbols. BTW it was linked with dietlibc-0.28 if possible, try with a non 3.4.x compiler too (if that fails for whatever reason) Works fine