On Thu, 22 Jul 2010, Isaac Levy wrote:
Hi ike,
long time no see.
I could be doing something stupid, or I've dug up an old bug, =
(http://www.mail-archive.com/freebsd-jail@freebsd.org/msg00859.html).
I cannot get good ol' trusty enforce_statfs to work, allowing me to see =
different mounts fro
Hi All,
I could be doing something stupid, or I've dug up an old bug,
(http://www.mail-archive.com/freebsd-jail@freebsd.org/msg00859.html).
I cannot get good ol' trusty enforce_statfs to work, allowing me to see
different mounts from within a jail.
--
The example jail command I'm using, (new-s
On Thu, 4 Jun 2009, Boris Samorodov wrote:
Hi,
There is definitely some inconsistency. JAIL(8) at recent
CURRENT talk about security.jail.param.allow.sysvipc and
it is listed via "sysctl -d security.jail.param". But seems
not to be used:
- at the jail -
# sysctl security.jail.param.allo
On Wed, 03 Jun 2009 13:05:03 +0200 Henrik Lidström wrote:
> Quoting "Bjoern A. Zeeb" :
> > On Sun, 31 May 2009, Boris Samorodov wrote:
> >
> > Hi,
> >
> >> has something changed at CURRENT with sysvipc jail handling?
> >> This jail has been working fine for almost a year.
> >>
> >> I've upgrade C
On Sun, 31 May 2009, Boris Samorodov wrote:
Hi,
has something changed at CURRENT with sysvipc jail handling?
This jail has been working fine for almost a year.
I've upgrade CURRENT to yesterday's sources and can't start
postgresql in a jail anymore:
- the jail -
% tail -2 /var/log/mess
Hello List,
has something changed at CURRENT with sysvipc jail handling?
This jail has been working fine for almost a year.
I've upgrade CURRENT to yesterday's sources and can't start
postgresql in a jail anymore:
- the jail -
% tail -2 /var/log/messages
May 31 18:22:47 pg postgres[55425