On Tue, 5 Aug 2003, Herbert P�tzl wrote:
> well, /var/run/vservers/<name>.ctx usually contains the
> context number and profile, so there should be such a file
> if the vserver is displayed in vserver-stat, simply renaming
> this file to XXX.ctx should be sufficient ...
How about this
{/var/run/vservers}# ll
total 8
-rw-r--r-- 1 root root 27 Jul 30 15:58 rpt.ctx
-rw-r--r-- 1 root root 27 Jul 30 15:58 rt.ctx
> on the other hand, if you lost your server somehow ;)
> and vserver-stat doesn't display it, the simples way would
> be to chcontext to this context and kill all processes
> and unmount any mounts into the chrooted environment ...
and this
{/var/run/vservers}# vserver-stat
CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME DESCRIPTION
0 30 28MB 1kB 57m49.96 1m56.86 5d09h43 root server
5 11 157MB 19kB 2m44.75 m08.57 5d04h40
6 4 6MB 524B 19m07.78 m33.08 5d04h30 rpt Report Generator
7 3 4MB 400B m13.13 m08.28 5d04h30 rt Request Tracker
I said it was strange.
I'm going to try a complete vserver restart and see what happens.
After about 5 tries and some editing of the .conf files to set context
numbers I got it back to looking mostly normal.
{/etc/vservers}# vserver-stat
CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME DESCRIPTION
0 30 28MB 1kB 1h20m04 2m50.19 5d09h53 root server
5 10 123MB 23kB m01.12 m00.04 m34.18 rt Request Tracker
7 4 6MB 687B m00.01 m00.00 m40.22 rpt Report Generator
Thanks for making me think ... harder on this. As to why/what happened
I'm totally clueless but it works so I'm happy.
Cheers,
Rod
--
"Open Source Software - Sometimes you get more than you paid for..."
