Re: [vserver] Cloning Gentoo vserver guest error

Hey. I've been here before.

I think Dennis missed an asterisk.

    ls -la /etc/vservers/*/vdir

Rod

-- 
On 10/06/2014 11:19 AM, John A. Wallace wrote:
> Hi, Dennis.  When I did the command you mentioned, it appeared to me that
> the first part worked fine, showing the files I would expect to see at
> "/etc/vservers", namely:
>
> .defaults
> .distributions
> VS1
> VS2
> VS3
> Etc...
>
> However, the second part of the command does appear to have a problem,
> showing this:
>
> "ls: cannot access /etc/vservers//vdir: No such file or directory".
>
> Which symbolic link, as you mentioned, is missing?
>
>
>
>> -----Original Message-----
>> From: Dennis Roos [mailto:dennis.roos@gmail.com]
>> Sent: Monday, October 06, 2014 4:42 AM
>> To: John Wallace
>> Cc: vserver@list.linux-vserver.org
>> Subject: Re: [vserver] Cloning Gentoo vserver guest error
>>
>> Dear John,
>>
>>
>> Start with an ls -la /etc/vservers/ && ls -la /etc/vservers//vdir  my
>> guess is that either the symlink is broken (points to a non-existing
>> path) or the directory doesn't exist at all.
>>
>> Kind regards,
>> Dennis Roos
>>
>>
>> On Oct 6, 2014, at 4:16 , John Wallace wrote:
>>
>>> When I tried cloning an existing, fully functional Vserver guest
>> running Gentoo, I get the following error:
>>>
>>> "/usr/lib/util-server/functions: line 83: cd : /etc/vservers//vdir:
>> No such file or directory"
>>>
>>> (That is not a typo with double slashes between vservers and vdir.)
>>>
>>> Here is what I see in util-vserver lines 81-84:
>>>
>>> function getPhysicalDir
>>> {
>>>     (set -P && cd "$1" && pwd)
>>> }
>>>
>>> I am not a programmer and cannot see whether there is any error in
>> that code. I know that I have cloned in the past using the same method
>> but with a Debian guest, not Gentoo, and I have surely updated a few
>> programs since then. I am using Gentoo Linux 3.13.11-vs2.3.6.11 on the
>> host. The installed version of util-vserver is 0.30.216_pre3038. If
>> someone has an idea about how to troubleshoot this, I would appreciate
>> hearing about it, and I can provide additional information if
>> necessary.
>>>
>>>
>
>
>