Herbert Poetzl said:
>> They appear production stable.
>
> what about the 'known' grsec-vserver incompatibilities?
>
I have not encountered any bugs that have caused my vservers to crash, or
had a security exploit, or data corruption...
I was not aware their were any major bugs.
Grsec has preven
On Fri, Jan 07, 2005 at 02:02:07AM -0700, Lucas Albers wrote:
>
> Herbert Poetzl said:
> > well, I'd say you added the S_CONTEXT=100 after you
> > encountered the first issues ... but you can check
> > with the lsxid tool doing
> >
> > lsxid /vservers/web1/etc/init.d/rc
> > lsxid /vservers
Hi Lucas,
> 1.)I cannot find the lsxid command for debian, even after doing a google
> for it.
they are part of the alpha tools. Currently there's no "official" Debian
package for those utils but only for the stable ones. We're working on
changing that. If you want to try the alpha-util-vserver d
Herbert Poetzl said:
> well, I'd say you added the S_CONTEXT=100 after you
> encountered the first issues ... but you can check
> with the lsxid tool doing
>
> lsxid /vservers/web1/etc/init.d/rc
> lsxid /vservers/web1/bin/bash
>
> and you can probably fix it by doing:
>
> mv /vse
On Thu, Jan 06, 2005 at 09:13:36AM -0700, Lucas Albers wrote:
> Running the 29 version of vserver.
>
> When I enable quota's, i am unable to start a vserver.
>
> The steps I follow are:
>
> #enabled config option in kernel.
> CONFIG_INOXID_GID24=y
> #installed kernel..
> #created ext3 file syste
Running the 29 version of vserver.
When I enable quota's, i am unable to start a vserver.
The steps I follow are:
#enabled config option in kernel.
CONFIG_INOXID_GID24=y
#installed kernel..
#created ext3 file system
mkfs -t ext3 /dev/sda1
#mounted system with options.
mount -t ext3 -o tagctx /de
