https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283934
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283934
--- Comment #1 from cr...@rlwinm.de ---
The parser does not crash if the expansion contains any string literals e.g.
these report **non**-fatal warnings and expand $x to empty string:
$y += ",$x";
$z += "$x,";
while this cr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283934
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are receiv
On 2021-06-07 00:04, Milan Obuch wrote:
> I need more interfaces moved this way. It is no problem issue
> manually
>
> ifconfig re3 vnet jail0
>
> but trying to write
>
> jail0
> {vnet;
> vnet.interface = re2;
> vnet.interface = re3;
> }
>
> in ja
On Sun, 06 Jun 2021 09:23:58 -0700, James Gritton
wrote:
> On 2021-06-06 06:35, Milan Obuch wrote:
> > Hi,
> >
> > for vnet jails, one needs to move some interface into created
> > virtual stack. In jail.conf, this could be achieved using
> >
> > jail0
On 2021-06-06 06:35, Milan Obuch wrote:
Hi,
for vnet jails, one needs to move some interface into created virtual
stack. In jail.conf, this could be achieved using
jail0
{vnet;
vnet.interface = re2;
}
and initialize moved interface using standard /etc/rc.conf
configuration
file in jail
Hi,
for vnet jails, one needs to move some interface into created virtual
stack. In jail.conf, this could be achieved using
jail0
{vnet;
vnet.interface = re2;
}
and initialize moved interface using standard /etc/rc.conf configuration
file in jail jail0.
Adding small paragraph about this in
I built a jail according to the handbook. I cannot find this configuration
file. Do I create it? Am I supposed to use the same up address as the host for
jails ip? If I were to give it a different ip address where am I to get this
second ip address? Please help thank you. Also I looked at /etc/r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245627
Dan Langille changed:
What|Removed |Added
CC||d...@freebsd.org
--- Comment #4 fro
from Jamie Gritton ---
While it would make sense for something like poudriere to work with the
existing jail.conf setup, that's non-trivial and not urgent. It seems
reasonable to add an rc knob for rc.d/jail to not remove all jails, and keep
the default behavior as is.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245627
--- Comment #2 from Kyle Evans ---
I think it's a bit odd to rule that it should be closed with absolutely no
action (perhaps documentation at a minimum) to be taken. Having jails while
also using tools like poudriere that create transient
--- Comment #1 from jo...@a1poweruser.com ---
Jail definition statements can still be placed in rc.conf which is the pre
release 6.0 method or in the jail.conf file which is the new way since release
6.0. The code in rcd/jail needs to be cleaned up removing the processing of the
old rc.conf jail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245627
Kyle Evans changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
CC|
Hi Jamie,
Thanks for the quick answer. I guess I have to decide to go full
command-line or full jail.conf.
The devctl patch seems pretty cool. Actually, I like the idea to have a
jaild daemon that take care of all the pre/post start/stop stuff, doable if
the devctl notifications system is in place
If I'm reading it right, then yes the behavior on creating jails if
intended. The defaults in jail.conf are only defaults to the jails listed
in jail.conf, not defaults to command-line-generated jails. So even if you
only include an empty block for the jail, it then is a jail.conf jail and
Hi all,
I have 2 silly questions and I think I know the answer.
I'd like to use the command line jail tool start and configure my jails;
however, I'd like to have defaults set up in a central place.
I thought I could put those defaults in /etc/jail.conf and then dynamically
create my
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238517
Jamie Gritton changed:
What|Removed |Added
Assignee|j...@freebsd.org|ja...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238517
--- Comment #3 from matthias+freebsd+bugzi...@harz.de ---
Perhaps the culprit is that I mount the jail root.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238517
--- Comment #2 from matthias+freebsd+bugzi...@harz.de ---
Created attachment 205029
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205029&action=edit
mymail jail.conf
--
You are receiving this mail because:
You are the a
from Jamie Gritton ---
Nothing has changed in the unmounting of filesystems on jail stop, and this is
a feature known to still work. It would be useful to see your jail.conf, to
get to the bottom of what's not working in your case.
There is the issue that is the jail stops "on its own&q
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238517
Mark Linimon changed:
What|Removed |Added
Keywords||regression
Assignee|b...@
On Wed, October 25, 2017 8:58 am, Steve Wills wrote:
> Hi,
>
> I created a patch which adds support for setting the cpu-list of a jails
> cpuset in jail.conf, here:
>
> https://reviews.freebsd.org/D12789
>
> If anyone finds this useful or has comments, please let me know.
Steve Wills wrote on 2017/10/25 15:58:
Hi,
I created a patch which adds support for setting the cpu-list of a jails
cpuset in jail.conf, here:
https://reviews.freebsd.org/D12789
If anyone finds this useful or has comments, please let me know.
It looks much better than my workaround:
alpha
Hi,
I created a patch which adds support for setting the cpu-list of a jails
cpuset in jail.conf, here:
https://reviews.freebsd.org/D12789
If anyone finds this useful or has comments, please let me know.
Thanks,
Steve
___
freebsd-jail@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218154
Jamie Gritton changed:
What|Removed |Added
CC||ja...@freebsd.org
Assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218154
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-jail@FreeBSD.org
vnet jail has to be started. But here "started"
does not have the normal meaning. A vnet jail can be created, jail -c,
and as long as there is no "exec.start sh /etc/rc" command in the
jail.conf definition there is nothing running in the jail. Now your
script has a jid
On 2017-02-17 10:58, Jeff Kletsky wrote:
...
I've been thinking about that for a while, especially as there isn't a
way to "catch" an execution error in jail(8) itself, such as the vnet
transition failing. (Yes, I'll open an issue on that once I'm convinced
I can't do it with the current jail fun
Thanks again for your thoughts on this.
I *am* using "pure" jail(8) and jail.conf(5) techniques and have been
for many years now. What I'd like to get to is a robust way to start
jails the way I have been
# jail -c some_jail
and just have it work reliably, especially when
tart -- 'ifconfig interface vnet jail'-like things
'jexec jail sh /etc/rc > ${exec.consolelog}'
Is there a better approach that someone out there knows of?
Thanks!
Jeff
Lets make this simple. Do not use the "service jail jailname start"
c
re a patch available to allow substitution of "array" parameters
>> into the strings used for exec.prestart, exec.poststop, and the like?
>>
>> [...]
> An alternate method to coding the jail.conf vnet.interface parameter
is to use the "ifconfig vnet" comman
I'm open to ideas here, including if I can somehow "write back" to
vnet.interface based on exec.prestart parsing the "custom" variables.
TIA,
Jeff
An alternate method to coding the jail.conf vnet.interface parameter is
to use the "ifconfig vnet" command
TL;DR
Is there a patch available to allow substitution of "array" parameters
into the strings used for exec.prestart, exec.poststop, and the like?
Longer:
I'd like to be able to use array parameters in exec.* commands,
but trying to do so results in
jail: test-two: exec.prestart: array cann
rent network interfaces)?
>>>
>>> Say, on host system:
>>>
>>> ifconfig_igb0="inet 172.20.9.22 ...
>>> ifconfig_igb1="inet 10.1.1.17 ...
>>>
>>>
>>> and in some jail
>>>
>>> $ip4_addr
#x27;t work for me in the past when
configured jails old style in /etc/rc.conf
I can't answer that because I have never tried it before.
More IP addresses on more interfaces works for me for many years even in
old rc.conf style jails.
Converted to new jail.conf is something like this
costa
s old style in /etc/rc.conf
I can't answer that because I have never tried it before.
Those exec. will give you a very fine-grained control over which commands
are run at the host environment (exec.prestart, exec.poststop, exec.poststart)
or within the jail's environment (exec.start, ex
>> jail_reverse_stop="YES"
>> jail_list="dns mail …”
>
> Awesome! For my use, I’m averse to starting jails at host boot- so I’m
> really excited this works.
It works very well (for quite some years now).
> Thanks so much Michael- this totally a
s that a variable to be expanded, or some other behavior?
>
> This is described in jail.conf(5) under the section "variables". I do have 10
> jails running, and those $ variables/parameters are very helpful, indeed.
I get it, the man page explained it well.
>
>>> Aga
Isaac (.ike) Levy wrote
> Wow, that’s rad Michael,
>
>> On Dec 14, 2016, at 3:30 PM, Michael Grimm wrote:
>>
>> Isaac (.ike) Levy wrote:
>>
>>> Can I specify multiple IP interfaces and assign IP’s to them using
>>> jail.conf?
>>
>
Wow, that’s rad Michael,
> On Dec 14, 2016, at 3:30 PM, Michael Grimm wrote:
>
> Isaac (.ike) Levy wrote:
>
>> Can I specify multiple IP interfaces and assign IP’s to them using jail.conf?
>
> Not sure if I understand your question correctly, but I do define the
>
Isaac (.ike) Levy wrote:
> Can I specify multiple IP interfaces and assign IP’s to them using jail.conf?
Not sure if I understand your question correctly, but I do define the following
in my jail.conf for VNET jails:
#
# host dependent global settings
#
$ip6prefixLOCAL = &q
>> In ezjail I can just do this:
>>
>
> Of course, it is great to learn that some tools can do this or that.
> However, this only is helpful to those who are just choosing what to use
> for the future. Once your choice is made, you (at least I) kind of avoid
> jumping over to doing something usi
While I appreciate the post, and the syntax is certainly cool to see, my
question is not about ezjail- I would ask questions about ezjail on whatever
respective list there is for that project.
My question is about the relatively new and slick jail.conf(1) and jail_set(2)
subsystems in base.
Best
> On Dec 14, 2016, at 8:31 AM, Valeri Galtsev wrote:
>
>>> no, this is not possible. Jail can only have one IP address (in addition
>>> to loopback addresses).
>>
>> Do you mean this just for jail.conf configuration/usage?
>
> No, that was earlier, i
e:
>>>> Hi All,
>>>>
>>>> Can I specify multiple IP interfaces and assign IPâÂÂs to them
>>>> using
>>>> jail.conf?
>>>> I have jails with IPv4/IPv6 addresses on multiple physical interfaces,
>>>> as
>>>
multiple IP interfaces and assign IPâÂÂs to them using
>>> jail.conf?
>>> I have jails with IPv4/IPv6 addresses on multiple physical interfaces,
>>> as
>>> well as assigning a loopback.
>>
>> Last time I tried it which was about year and a half ago
On 14/12/16 03:21, Ian Smith wrote:
> On Wed, 14 Dec 2016 10:09:58 +0800, Ernie Luzar wrote:
>
> > I recommend you check out these ports,
> > jail-primer gives background on jails across Freebsd releases.
> > qjail a utility that simplifies jail admin.
>
> Joe Barbish,
>
> please stop using resp
On 2016-12-13 23:47, Isaac (.ike) Levy wrote:
> Hi Valeri,
>
>> On Dec 13, 2016, at 5:03 PM, Valeri Galtsev
>> wrote:
>>
>> On Tue, December 13, 2016 2:14 pm, Isaac (.ike) Levy wrote:
>>> Hi All,
>>>
>>> Can I specify multiple IP interf
Hi Valeri,
> On Dec 13, 2016, at 5:03 PM, Valeri Galtsev wrote:
>
> On Tue, December 13, 2016 2:14 pm, Isaac (.ike) Levy wrote:
>> Hi All,
>>
>> Can I specify multiple IP interfaces and assign IPâs to them using
>> jail.conf?
>> I have jails with I
Oh,
> On Dec 13, 2016, at 10:21 PM, Ian Smith wrote:
>
> On Wed, 14 Dec 2016 10:09:58 +0800, Ernie Luzar wrote:
>
>> I recommend you check out these ports,
>> jail-primer gives background on jails across Freebsd releases.
>> qjail a utility that simplifies jail admin.
>
> Joe Barbish,
>
> ple
Thanks Ernie,
But, that straight out did not work for me,
> On Dec 13, 2016, at 9:09 PM, Ernie Luzar wrote:
>
> Isaac (.ike) Levy wrote:
>> Hi All,
>> Can I specify multiple IP interfaces and assign IP’s to them using jail.conf?
>> I have jails with IPv4/IPv6 add
On Wed, 14 Dec 2016 10:09:58 +0800, Ernie Luzar wrote:
> I recommend you check out these ports,
> jail-primer gives background on jails across Freebsd releases.
> qjail a utility that simplifies jail admin.
Joe Barbish,
please stop using responses to people's issues to advertise your ports.
Isaac (.ike) Levy wrote:
Hi All,
Can I specify multiple IP interfaces and assign IP’s to them using jail.conf?
I have jails with IPv4/IPv6 addresses on multiple physical interfaces, as well
as assigning a loopback.
I have not found answers in the respective man pages or digging online.
I’m
On Tue, December 13, 2016 2:14 pm, Isaac (.ike) Levy wrote:
> Hi All,
>
> Can I specify multiple IP interfaces and assign IPâs to them using
> jail.conf?
> I have jails with IPv4/IPv6 addresses on multiple physical interfaces, as
> well as assigning a loopback.
Last time I
Hi All,
Can I specify multiple IP interfaces and assign IP’s to them using jail.conf?
I have jails with IPv4/IPv6 addresses on multiple physical interfaces, as well
as assigning a loopback.
I have not found answers in the respective man pages or digging online.
I’m finally starting to poke
to the new
base.
On Thu, Oct 29, 2015, 08:19 Miroslav Lachman <000.f...@quip.cz> wrote:
> Clint Armstrong wrote on 10/29/2015 12:53:
> > A little while ago I wrote up an overview of how I build jails using
> > jail.conf at http://clinta.github.io/freebsd-jails-the-hard-way/.
Clint Armstrong wrote on 10/29/2015 12:53:
A little while ago I wrote up an overview of how I build jails using
jail.conf at http://clinta.github.io/freebsd-jails-the-hard-way/.
I noticed your are using unionfs. Is it working without any problems?
Every time (in the past) I read that somebody
A little while ago I wrote up an overview of how I build jails using
jail.conf at http://clinta.github.io/freebsd-jails-the-hard-way/.
On Wed, Oct 28, 2015 at 6:29 PM Philip Jocks
wrote:
>
> > Am 28.10.2015 um 22:05 schrieb Miroslav Lachman <000.f...@quip.cz>:
> >
> >
gt;>> Valeri Galtsev wrote:
>>>>> Dear All,
>>>>>
>>>>> Can someone recommend something similar to FreeBSD handbook that
>>>>> describes
>>>>> building jails for newer systems meaning /etc/jail.conf as opposed to
>>>>
systems meaning /etc/jail.conf as opposed to
/etc/rc.conf which handbook currently has in its jails chapter. I
still
have all jail configurations on 9.3 boxes in /etc/rc.conf, but it is
time
to build 10.x production boxes, and do things modern way (implying
/etc/jail.conf). I still intend to keep
gt; > building jails for newer systems meaning /etc/jail.conf as opposed to
>> > /etc/rc.conf which handbook currently has in its jails chapter. I
>> > still
>> > have all jail configurations on 9.3 boxes in /etc/rc.conf, but it is
>> > time
>> > to b
On Wed, 2015-10-28 at 13:27 -0400, Ernie Luzar wrote:
> Valeri Galtsev wrote:
> > Dear All,
> >
> > Can someone recommend something similar to FreeBSD handbook that
> > describes
> > building jails for newer systems meaning /etc/jail.conf as opposed to
> >
Hi there,
I'm running some jail servers on 10.2-RELEASE without VIMAGE or
something like that but using jail(8) and jail.conf(5).
Something seems to be wrong on my jail.conf but I wasn't able to track
this down.
For example (output with additional l
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196574
Hiroki Sato changed:
What|Removed |Added
Assignee|freebsd-jail@FreeBSD.org|h...@freebsd.org
Status|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196574
erdge...@erdgeist.org changed:
What|Removed |Added
CC||erdge...@erdgeist.org
--- C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196574
Glen Barber changed:
What|Removed |Added
CC||h...@freebsd.org
--- Comment #2 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196574
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-jail@FreeBSD.org
--
You ar
n script) without
>> any other confg files and customization
>> This tool is written on Python, also work only with vnet, zfs
>> and FreeBSD 10 (probably will work on FreeBSD 9.1 but i never
>> test it)
>> JADM work only with n
On 2014-05-13 07:11, fb...@a1poweruser.com wrote:
I think you have made some poor basic design choices.
Let him scratch his itch. Maybe it solves a problem you haven't
encountered yet?
1. Requiring python as a dependent. Thats a lot of overhead just for a
script. Not a show stopper, but a
ol is written on Python, also work only with vnet, zfs and
FreeBSD 10 (probably will work on FreeBSD 9.1 but i never test it)
JADM work only with native /etc/jail.conf
When is started for first time jadm generate new /etc/jail.conf in
special format developed by me.
jail.conf file can be use
ce) support
>> The idea is to have a single application (python script) without any
>> other confg files and customization
>> This tool is written on Python, also work only with vnet, zfs and
>> FreeBSD 10 (probably will work on FreeBSD 9.1 but i never test it)
>> JADM
application (python script) without any
> other confg files and customization
> This tool is written on Python, also work only with vnet, zfs and
> FreeBSD 10 (probably will work on FreeBSD 9.1 but i never test it)
> JADM work only with native /etc/jail.conf
> When is started fo
only with vnet, zfs and
FreeBSD 10 (probably will work on FreeBSD 9.1 but i never test it)
JADM work only with native /etc/jail.conf
When is started for first time jadm generate new /etc/jail.conf in
special format developed by me.
jail.conf file can be used and without JADM.
for more inform
On Sun, 23 Feb 2014 09:11:43 +0200
Folder wrote:
> Hi,
>
> I have used freeb up to 9 release by now. I now installed
> FreeBSD 10.0-RELEASE and I am very disappointed with the new jail
> setup.
> One of the reasons is that using devfs_ruleset has no eff
Hi,
I have used freeb up to 9 release by now. I now installed
FreeBSD 10.0-RELEASE and I am very disappointed with the new jail setup.
One of the reasons is that using devfs_ruleset has no effect
in jail.conf.
example:
DDNS {
host.hostname = "DDNS"
> The IP should only be brought up and down if there's an interface
> mentioned in the jail config.
In jail.config specify IP address only and remove reference to interface (re1)
Brilliant. Works like a charm - thank you very much.
-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View t
On 2/4/2014 6:19 AM, Beeblebrox wrote:
I have two NIC's, re1 faces internal LAN. re1 also has a jail running on it
for diskless clients (tftp, dhcp). IP assigned to re1 by /etc/rc.conf and
jail.conf are same: ip4.addr = 192.168.2.1/24
A /32 subnet will break diskless clients and also pre
I have two NIC's, re1 faces internal LAN. re1 also has a jail running on it
for diskless clients (tftp, dhcp). IP assigned to re1 by /etc/rc.conf and
jail.conf are same: ip4.addr = 192.168.2.1/24
A /32 subnet will break diskless clients and also prevents gatewaying of
traffic from la
On 10/18/2013 2:42 PM, Dirk Engling wrote:
Dear jail enthusiasts,
in order to move forward with my jail management project ezjail, and
make it support the new jail.conf way of managing jail configs, I need a
way to add properties to jails that are currently not in the list of
allowed parameters
Dear jail enthusiasts,
in order to move forward with my jail management project ezjail, and
make it support the new jail.conf way of managing jail configs, I need a
way to add properties to jails that are currently not in the list of
allowed parameters. I was thinking of something like
web-jail
Jamie Gritton wrote:
[...]
Hi Jamie,
I tried your suggestion with exec_poststart for setting the cpuset.
It doesn't work. I don't know if it worked for you with any older
version of FreeBSD. I tried it on FreeBSD 9.1-RELESE.
I have this in rc.conf
jail_fox_exec_poststart0="cpuset -c -l 5-6 -
Jamie Gritton wrote:
On 03/17/13 05:59, Nicolas de Bari Embriz Garcia Rojas wrote:
Hi, all, I am start using the jail.conf for running my jails, in
rc.local I have this line jail -c this to start my jails at boot time
(any better ideas)
Now checking the man pages for the jail I found a option
Marek Rudnicki wrote:
Hello
I have a jail configuration in /etc/jail.conf and can start it with:
# jail -c myjail
However, I would like to start it automatically at system boot, e.g. by
using /etc/rc.conf . What's the best way to do that?
And generally, is it the recommended w
Hello
I have a jail configuration in /etc/jail.conf and can start it with:
# jail -c myjail
However, I would like to start it automatically at system boot, e.g. by
using /etc/rc.conf . What's the best way to do that?
And generally, is it the recommended way to configure jail in
lambert@nagios1:~>
> -Original Message-
> From: Lars Engels [mailto:lars.eng...@0x20.net]
> Sent: Wednesday, June 26, 2013 2:00 PM
> To: Ivailo Tanusheff
> Cc: wishmaster; freebsd-jail@freebsd.org
> Subject: Re: Re[2]: Loopback and jail.conf
>
> On Wed, Jun 26, 2
On Wed, Jun 26, 2013, at 7:12, Ivailo Tanusheff wrote:
> I need all jails to use the 127.0.0.1 address, not different hosts in
> 127.0.0 network.
>
Jails cannot all share the same loopback. The networking in a jail is a
bit odd if you're new to it. If you really want each jail to act like
its own
jail.conf
On Wed, Jun 26, 2013 at 07:47:25AM +, Ivailo Tanusheff wrote:
> Mate, I do not need pf or ipfw :)
> Maybe I did not describe it well, what I simply need is:
>
> Jail 1:
> Interface em0: 192.168.0.1
> Interface lo0: 127.0.0.1
>
> Jail 2:
>
2:
> jail: jail2: IPv4 addresses clash
>
> What I use in jail.conf:
>
> Jail1: ip4.addr = 192.168.0.1 , 127.0.0.1;
> Jail2: ip4.addr = 192.168.0.2 , 127.0.0.1;
You can add aliases to lo0: 127.0.0.2, .3, .4, ...
pgpnWVX_WnJdo.pgp
Description: PGP signature
see, there the same address for the loopback, which gives me an
error when I start the jail:
Jail 1 starts ok.
Then when I start Jail 2:
jail: jail2: IPv4 addresses clash
What I use in jail.conf:
Jail1: ip4.addr = 192.168.0.1 , 127.0.0.1;
Jail2: ip4.addr = 192.168.0.2 , 127.0.0.1;
-Original
Hi,
I'm trying to use the new jail.conf configuration for several jails on a single
host.
Due to some software limitations I need to have the loopback set on all jails,
e.i. for each jail I need something like:
lo0: flags=8049 metric 0 mtu 16384
options=63
inet 127.
On 03/31/13 21:53, Ian Smith wrote:
> On Sun, 31 Mar 2013 22:58:33 +0200, Dirk Engling wrote:
>> Maybe meeting at a BSDcon over a beer would help ;)
>
> Unlikely to hurt, anyway :)
Perhaps I need to plan on going to BSDCan after all...
- Jamie
___
fre
On Sun, 31 Mar 2013 22:58:33 +0200, Dirk Engling wrote:
> On 31.03.13 22:01, Miroslav Lachman wrote:
>
> >> So I guess, I am out of luck here, because users used to think of their
> >> jails as what they saw in the hostname field on jls. If I am writing
> >> tools that use jail_getid to map t
On 2013-04-1 04:01 , Paul Schenkeveld wrote:
On Sun, Mar 31, 2013 at 09:14:23PM +0200, Dirk Engling wrote:
On Sun, 31 Mar 2013, Jamie Gritton wrote:
If you don't mind some slightly difficult error messages, you can always
"disable" a jail with exec.prestart="false". jail(8) requires all
comma
On 03/31/13 14:58, Dirk Engling wrote:
On 31.03.13 22:01, Miroslav Lachman wrote:
So I guess, I am out of luck here, because users used to think of their
jails as what they saw in the hostname field on jls. If I am writing
tools that use jail_getid to map the jailname to the jid, it will never
On 03/31/13 20:01, Paul Schenkeveld wrote:
On Sun, Mar 31, 2013 at 09:14:23PM +0200, Dirk Engling wrote:
On Sun, 31 Mar 2013, Jamie Gritton wrote:
If you don't mind some slightly difficult error messages, you can always
"disable" a jail with exec.prestart="false". jail(8) requires all
command
On Sun, Mar 31, 2013 at 09:14:23PM +0200, Dirk Engling wrote:
>
> On Sun, 31 Mar 2013, Jamie Gritton wrote:
>
> > If you don't mind some slightly difficult error messages, you can always
> > "disable" a jail with exec.prestart="false". jail(8) requires all
> > commands to succeed, and in particul
On 31.03.13 22:01, Miroslav Lachman wrote:
>> So I guess, I am out of luck here, because users used to think of their
>> jails as what they saw in the hostname field on jls. If I am writing
>> tools that use jail_getid to map the jailname to the jid, it will never
>> match that hostname and I also
sorry for misinform you with name=myjail in rc.conf, I didn't try
it because I am using an old way with -n jailname on my older boxes and
I am planing to use new syntax only with jail.conf (after problem with
mounting of devfs will be fixed).
So I guess, I am out of luck here, becau
On Sun, 31 Mar 2013, Jamie Gritton wrote:
If you don't mind some slightly difficult error messages, you can always
"disable" a jail with exec.prestart="false". jail(8) requires all
commands to succeed, and in particular won't even create a jail when one
of the prestart commands fails.
This vi
On 03/31/13 12:58, Dirk Engling wrote:
On 31.03.13 20:31, Jamie Gritton wrote:
That seems reasonable, but using a jail list in rc.conf may suffice.
It is less error prone to just use 'jail_list=*' in rc.conf and disable
jails per config block, and then issue a warning like 'Skipping disabled
1 - 100 of 123 matches
Mail list logo
