hi,
ls -la und host system:
shell1:/vservers# ls -la
total 44
drwxrwxrwx 11 root root 4096 Jul 10 19:19 .
drwxr-xr-x 24 root root 4096 Feb 2 05:49 ..
drwxrwxrwx 2 root root 4096 Feb 2 07:11 ARCHIVES
drwxrwxrwx 20 root root 4096 Jul 10 22:16 eggdrop
drwxrwxrwx 21 root root 4096 Jul 10 19:05 f_jeromin
drwxrwxrwx 19 root root 4096 Jul 10 17:14 m_schmidtke
drwxrwxrwx 19 root root 4096 Jul 10 19:26 r_vornholt
drwxrwxrwx 19 root root 4096 Jul 10 19:23 s_dzepina
drwxrwxrwx 20 root root 4096 Jul 10 22:13 s_meyer
drwxrwxrwx 20 root root 4096 Jul 10 22:09 shell2
drwxrwxrwx 19 root root 4096 Jul 10 10:10 t_walther
by the way:
shell1:/vservers# vserver eggdrop enter
**********************************************************
/vservers/eggdrop/.. has insecure permissions.
A vserver administrator may be able to visit the root server.
To fix this, do
chmod 000 /vservers/eggdrop/..
do it anytime you want, even if vservers are running.
**********************************************************
so not only /vserver have to be chmod 000 but /vservers/*
but then appears:
can`t chroot dir
strange =)
Greetings
Oliver
-----Original Message-----
From: Nuno Silva [mailto:[EMAIL PROTECTED]
Sent: Freitag, 11. Juli 2003 21:33
To: [EMAIL PROTECTED]
Subject: Re: [vserver] mkdir: cannot create directory `test': Permission
denied after vserver crash
Oliver Dzombic wrote:
> hi chris,
>
> ls -l of / in real server:
>
> d--------- 11 root root 4096 Jul 10 19:19 vservers
>
[..snip..]
>
> -----Original Message-----
> From: Christoph Kuhles [mailto:[EMAIL PROTECTED]
[..snip..]
>
> You should chmod 000 /vservers/ ... not the directories within. At
> least that's what I think.
>
> Cheers
> Chris
>
That's right, so:
Show us the ls -la /vservers/
Regards,
Nuno Silva
