Re: New jail does not understand nullfs

--047d7b338f639dc41304cfe953d5
Content-Type: text/plain; charset=ISO-8859-1

Attached is my jail.conf. according to my logs I am using r243464. Going to
do another svn update and try again as well.
 On Dec 2, 2012 7:12 PM, "Mateusz Guzik" <mjguzik@gmail.com> wrote:

> On Sun, Dec 02, 2012 at 08:09:39AM -0700, Ian Lepore wrote:
> > On Sun, 2012-12-02 at 01:17 -0600, Matt Donovan wrote:
> > > When attempting to start the jail in question the following happens
> > >
> > >
> > > server# jail -c poudriere
> > > jail: poudriere: unknown parameter: allow.mount.nullfs
> > >
> > >
> > > Below is my jail.conf
> > >
> > > poudriere {
> > >          name=poudriere;
> > >          host.hostname=poudriere;
> > >         ip4.addr="192.168.1.30";
> > >        persist;
> > >         children.max=10;
> > >         allow.mount;
> > >          mount.devfs;
> > >       allow.mount.nullfs;
> > >       allow.raw_sockets;
> > >       allow.socket_af;
> > >       allow.sysvipc;
> > >       enforce_statfs=1;
> > >       path=/newsystem/jail/poudriere;
> > >       exec.stop="umount -a";
> > > }
> > >
> > > Does the switch not work yet? As I am using CURRENT with the latest
> > > revision.
> > >
> >
> > That "mount.devfs" doesn't look right, should that have "allow." on the
> > front?  I wonder if that's the problem and the error report is off by
> > one line or something?
> >
>
> mount.devfs means "mount devfs" :)
>
> However, it indeed may be some issue with config parsing, e.g. some
> mishandled whitespace.
>
> Matt, in general this should work just fine. What revision are you using
> to test? Can you attach this config instead of copy-pasting it?
>
> --
> Mateusz Guzik <mjguzik gmail.com>
>

--047d7b338f639dc41304cfe953d5
Content-Type: application/octet-stream; name="jail.conf"
Content-Disposition: attachment; filename="jail.conf"
Content-Transfer-Encoding: base64
X-Attachment-Id: 1420297164228824678-1

cG91ZHJpZXJlIHsKICAgICAgICAgbmFtZT1wb3VkcmllcmU7CiAgICAgICAgIGhvc3QuaG9zdG5h
bWU9cG91ZHJpZXJlOyAKICAgICAgICBpcDQuYWRkcj0iMTkyLjE2OC4xLjMwIjsgICAgICAKICAg
ICAgIHBlcnNpc3Q7IAogICAgICAgIGNoaWxkcmVuLm1heD0xMDsgCiAgICAgICAgYWxsb3cubW91
bnQ7CiAgICAgICAgIG1vdW50LmRldmZzOwogICAgICAgIGFsbG93Lm1vdW50Lm51bGxmczsKICAg
ICAgYWxsb3cucmF3X3NvY2tldHM7IAogICAgICBhbGxvdy5zb2NrZXRfYWY7CiAgICAgIGFsbG93
LnN5c3ZpcGM7IAogICAgICBlbmZvcmNlX3N0YXRmcz0xOwogICAgICBwYXRoPS9uZXdzeXN0ZW0v
amFpbC9wb3VkcmllcmU7IAogICAgICBleGVjLnN0b3A9InVtb3VudCAtYSI7IAp9Cg==
--047d7b338f639dc41304cfe953d5
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
--047d7b338f639dc41304cfe953d5--