A problem this time,
When using the new tools (with the legacy method), the
name of the vservers running on the system is empty and it is not
possible to enter/stop/start/... them. vserver-stat display the vservers,
processes, etc. however, name is empty too.
Has anyone already had this kind
i'm currently migrating my vservers to the new config-style.
the name of the vserver isn't displayed here neither, but i'm able to start
stop them _with_ the name (as usual).
the vserver prog then says assuming legacy mode
i guess you didn't compile your tools with the legacy api enabled...
On
On Mon, Jun 06, 2005 at 09:05:24AM -0400, Benoit des Ligneris wrote:
A problem this time,
When using the new tools (with the legacy method), the
name of the vservers running on the system is empty and it is not
possible to enter/stop/start/... them. vserver-stat display the vservers,
Hello,
Well, I have compiled them with the legacy utils because otherwise, I
was not able to start my legacy vservers ;-)
I have the same message than you have (i.e. : assuming legacy mode)
but I was not able to stop/restart them...
I will do some more testing tonight...
Ben
* Georges Toth
--- Herbert Poetzl [EMAIL PROTECTED] wrote:
On Mon, Jun 06, 2005 at 09:05:24AM -0400, Benoit des
Ligneris wrote:
A problem this time,
When using the new tools (with the legacy method),
the
name of the vservers running on the system is
empty and it is not
possible to
On Mon, Jun 06, 2005 at 08:50:42AM -0700, Eric Jorgensen wrote:
--- Herbert Poetzl [EMAIL PROTECTED] wrote:
On Mon, Jun 06, 2005 at 09:05:24AM -0400, Benoit des
Ligneris wrote:
A problem this time,
When using the new tools (with the legacy method),
the
name of the
