XvM5RnWQdN3AXCu4vmE2WggoAec6rJIsub9aT32nZINDq8g5W7iwrTPLI4DFrXLSXH7kxAy06C4q
gzdho6S4fPgaAk13x8N92JhAvQBjpov7WUmimbz7DlgmmPnqLvM7rTVY8JPb36VSUkqYHcpuzT3Ykxe
3HLU236FOg4iREkVv0GZlUkyVKXBa6gQ27vDXspMITWAjgjTUFYyJ061Gu5uqSDFl39Y2E
hihaRoOlChxj9xiS1Nsa7ffdMMFbDgXKN6uEtJ4krzqCMXunAQ7PHAeF9dCyO
fjb6LZfKccWWV0xyu9z2ddguLG8KIkbZDafFmKT5yjZALeKX0fgVCQ0pK9pOMvXn3FWQq0lLeCes
bLPZcdsil7bwXxTnumPvj5NelUeDnluhtJGhc9ZeotDLHmQGpuKgnN4KTAFSs1Aui2j9VsAd515srsU
z9JgB5dUmt6khxJu3RqCB8SKYlGPlsZ5XA9MOOYBHoKj2jJwh7Et1vAKfRJnUGB25b3Md6
1VYxfJk24epC1j9hotAkKaxEk2UFUfZfpoYJ4bXyQIuZEsSCcEUUhpCPQScwU
Daniel Hokka Zakrisson wrote:
Roderick A. Anderson wrote:
After making several copies/clones of a vserver I am getting the
following message when I try to install yum ( for internal pkgmgmt )
using vyum.
# vyum demo -- install yum
vlogin: execvp(): No such file or directory
You should pro
Roderick A. Anderson wrote:
After making several copies/clones of a vserver I am getting the
following message when I try to install yum ( for internal pkgmgmt )
using vyum.
# vyum demo -- install yum
vlogin: execvp(): No such file or directory
You should probably internalize package managem
After making several copies/clones of a vserver I am getting the
following message when I try to install yum ( for internal pkgmgmt )
using vyum.
# vyum demo -- install yum
vlogin: execvp(): No such file or directory
The guest I'm using to make copies from ( test ) was created using the
step
On Tue, Jun 27, 2006 at 10:34:52AM +0200, Christian Knauber wrote:
> Yes you can leave it without, but in this case if you defined it in
> the "old" vserver you would have to change it in the "new" vserver.
>
> Also, I do not know if this is really the case, but I felt that having
> fixed context I
Youri LACAN-BARTLEY a écrit :
> Hi Odile,
>
> you might have missed out on the vserver hostname.
> You should specify "new" in /etc/vservers/new/uts/nodename
>
> All the rest seems fine to me but I might also be missing something
> obvious,
>
> Good luck to you,
>
> Youri
>
Thanks, it works!!
> O
Yes you can leave it without, but in this case if you defined it in the "old"
vserver you would have to change it in the "new" vserver.
Also, I do not know if this is really the case, but I felt that having fixed
context IDs is much more stable than having dynamic ones.
- Original Message -
Hi,Have you changed the context number in /etc/vservers/new/context ?As I had lots of trouble changing config stuff when copying, I have a personal way for copy/duplicate:-make a new vserver skeleton named "new" with right ip, context, etc that way:
vserver [name] build -m skeleton --hostname [ho
IIRC, there is no need to manually specify the context ID ...
Christian Knauber wrote:
Did you change the context id of the new vserver ?
It is defined in the file /etc/vservers/new/context.
Have a nice day,
Christian
- Original Message -
From: Odile Bénassy <[EMAIL PROTECTED]>
To: vs
Did you change the context id of the new vserver ?
It is defined in the file /etc/vservers/new/context.
Have a nice day,
Christian
- Original Message -
From: Odile Bénassy <[EMAIL PROTECTED]>
To: vserver@list.linux-vserver.org
Sent: Tuesday, June 27, 2006 9:18:27 AM GMT+0100
Subject: [Vs
Hi Odile,
you might have missed out on the vserver hostname.
You should specify "new" in /etc/vservers/new/uts/nodename
All the rest seems fine to me but I might also be missing something obvious,
Good luck to you,
Youri
Odile Bénassy wrote:
Hello,
I hope not to disturb with a low-level que
Hello,
I hope not to disturb with a low-level question, I still hope will be
useful to others.
I'm very happy with my vservers in general, I must say, and the users
too, of course.
I want to copy a vserver into a second one, because the second one will
run the same software.
So I had an IP .xxx
13 matches
Mail list logo
