|
A
couple of possiblities:
You
are not logging in as admin? (in which case /usr/sbin, where rebootvs
resides, will not be accessible)
Your
skel was incorrectly built (should have seen errors during skel
generation)
Your
virtual server was incorrectly built (should have seen errors during virtual
server creation)...
With
regard to priviliges, try the vsdadm priv_modify command on the hosting server,
or if you are root within the virtual server manually edit the /etc/vsd/priv
file.
If you
want vsd commands available within your virtual servers, install freeVSD from
source within the VS, or incorporate it into your skel...
hi tim, when i connect virtual sever or host
server via telnet normally (without 1725) there are no vsd commands
available.(rebootvs etc.....)
how to set privileges????
----- Original Message -----
Sent: Monday, May 28, 2001 1:18
PM
Subject: RE: how to administrate
virtual server via telnet?
If
you connect to port 1725 on the hosting server you are connecting directly
to the VSD service defined in /etc/inetd.conf. This is not the way to
administer VSD servers. You should connect to your virtual server via telnet
(do not specify a specific port) and login. You may then manage your virtual
server via the command line in the usual manner. Altrenatively read
the enclosed doucmentation to see how to use vsdadm and the collection
of modules supplied...
Tim
hello,
what is the way to administrate virtual
servers via telnet?
telnet with port 1725 gives after some
seconds "++OK FreeVSD server...." the message: "ERR connection
closed"
this happened by connection over host and by
connection over virtual server, why?
thank you
niko
| 