Re: sysvipc only for one jail

2013-08-14 Thread David Demelier
On 12.08.2013 19:46, Trond Endrestøl wrote: On Mon, 12 Aug 2013 14:09+0200, Trond Endrestøl wrote: On Mon, 12 Aug 2013 13:57+0200, David Demelier wrote: 2013/8/12 Trond Endrestøl : On Mon, 12 Aug 2013 12:40+0200, David Demelier wrote: 2013/8/11 Maciej Suszko : Maciej Suszko wrote: [...]

Re: sysvipc only for one jail

2013-08-13 Thread Alejandro Imass
On Tue, Aug 13, 2013 at 12:14 AM, Shane Ambler wrote: > On 12/08/2013 21:39, Trond Endrestøl wrote: >> >> On Mon, 12 Aug 2013 13:57+0200, David Demelier wrote: > > >>> And thus, it's not enabled as postgresql tells: >>> >>> creating template1 database in /usr/local/pgsql/data/base/1 ... FATAL: >>>

Re: sysvipc only for one jail

2013-08-13 Thread Trond Endrestøl
On Tue, 13 Aug 2013 07:53-0400, Fbsd8 wrote: > What 9.3 are you talking about > 9.2-RC1 is the newest available. > Is 9.3 a typo and you really mean 9.2?? PostgreSQL 9.3beta2, you'll find it in ports as databases/postgresql93-server, etc. http://wiki.postgresql.org/wiki/What's_new_in_Postgr

Re: sysvipc only for one jail

2013-08-13 Thread Fbsd8
Terje Elde wrote: On 12. aug. 2013, at 19.46, Trond Endrestøl wrote: If you start the jail manually using jail(8), then /etc/jail.conf comes into play, whereas the lines in /etc/rc.conf is used during automatic startup of the jails when the host is rebooted. The whole arrangement seems unneces

Re: sysvipc only for one jail

2013-08-13 Thread Fbsd8
Shane Ambler wrote: On 12/08/2013 21:39, Trond Endrestøl wrote: While it is currently in beta maybe you could also try 9.3 and verify that the shared memory update works or eliminates this configuration? If you missed the change, 9.3 is implementing shared memory using mmap. What 9.3 are

Re: sysvipc only for one jail

2013-08-13 Thread Terje Elde
On 12. aug. 2013, at 19.46, Trond Endrestøl wrote: > If you start the jail manually using jail(8), then /etc/jail.conf > comes into play, whereas the lines in /etc/rc.conf is used during > automatic startup of the jails when the host is rebooted. The whole > arrangement seems unnecessary redunda

Re: sysvipc only for one jail

2013-08-12 Thread Terje Elde
On 13. aug. 2013, at 06:14, Shane Ambler wrote: > If you missed the change, 9.3 is implementing shared memory using mmap. But still using sysvipc for some locks/mutexes, so doesn't allow you to run "sysvipc-free". Terje ___ freebsd-questions@freebsd

Re: sysvipc only for one jail

2013-08-12 Thread Shane Ambler
On 12/08/2013 21:39, Trond Endrestøl wrote: On Mon, 12 Aug 2013 13:57+0200, David Demelier wrote: And thus, it's not enabled as postgresql tells: creating template1 database in /usr/local/pgsql/data/base/1 ... FATAL: could not create shared memory segment: Function not implemented I'll lo

Re: sysvipc only for one jail

2013-08-12 Thread Trond Endrestøl
On Mon, 12 Aug 2013 14:09+0200, Trond Endrestøl wrote: > On Mon, 12 Aug 2013 13:57+0200, David Demelier wrote: > > > 2013/8/12 Trond Endrestøl : > > > On Mon, 12 Aug 2013 12:40+0200, David Demelier wrote: > > > > > >> 2013/8/11 Maciej Suszko : > > >> > Maciej Suszko wrote: > > >> > [...] > > >>

Re: sysvipc only for one jail

2013-08-12 Thread Maciej Suszko
David Demelier wrote: > 2013/8/11 Maciej Suszko : > > Maciej Suszko wrote: > > [...] > >> > >> You can specify different params for each jail using _parameters, > >> for example: > >> > >> jail_jailname_params="allow.chflags=1 allow.sysvipc=1" > > > > Sorry, my mistake - it should be jail_jailnam

Re: sysvipc only for one jail

2013-08-12 Thread Trond Endrestøl
On Mon, 12 Aug 2013 13:57+0200, David Demelier wrote: > 2013/8/12 Trond Endrestøl : > > On Mon, 12 Aug 2013 12:40+0200, David Demelier wrote: > > > >> 2013/8/11 Maciej Suszko : > >> > Maciej Suszko wrote: > >> > [...] > >> >> > >> >> You can specify different params for each jail using _parameter

Re: sysvipc only for one jail

2013-08-12 Thread David Demelier
2013/8/12 Trond Endrestøl : > On Mon, 12 Aug 2013 12:40+0200, David Demelier wrote: > >> 2013/8/11 Maciej Suszko : >> > Maciej Suszko wrote: >> > [...] >> >> >> >> You can specify different params for each jail using _parameters, for >> >> example: >> >> >> >> jail_jailname_params="allow.chflags=1

Re: sysvipc only for one jail

2013-08-12 Thread Trond Endrestøl
On Mon, 12 Aug 2013 12:40+0200, David Demelier wrote: > 2013/8/11 Maciej Suszko : > > Maciej Suszko wrote: > > [...] > >> > >> You can specify different params for each jail using _parameters, for > >> example: > >> > >> jail_jailname_params="allow.chflags=1 allow.sysvipc=1" > > > > Sorry, my mis

Re: sysvipc only for one jail

2013-08-12 Thread David Demelier
2013/8/11 Maciej Suszko : > Maciej Suszko wrote: > [...] >> >> You can specify different params for each jail using _parameters, for >> example: >> >> jail_jailname_params="allow.chflags=1 allow.sysvipc=1" > > Sorry, my mistake - it should be jail_jailname_parameters= of course. > -- > regards, Ma

Re: sysvipc only for one jail

2013-08-11 Thread Maciej Suszko
Maciej Suszko wrote: [...] > > You can specify different params for each jail using _parameters, for > example: > > jail_jailname_params="allow.chflags=1 allow.sysvipc=1" Sorry, my mistake - it should be jail_jailname_parameters= of course. -- regards, Maciej Suszko. signature.asc Descriptio

Re: sysvipc only for one jail

2013-08-11 Thread Maciej Suszko
David Demelier wrote: > Hi, > > I would like to enable sysvipc only for one jail (defined in > /etc/rc.conf). It's possible with jail.conf but this is not supported > with jails listed in /etc/rc.conf. > > Is it possible without using the global jail_sysvipc_allow ?

sysvipc only for one jail

2013-08-11 Thread David Demelier
Hi, I would like to enable sysvipc only for one jail (defined in /etc/rc.conf). It's possible with jail.conf but this is not supported with jails listed in /etc/rc.conf. Is it possible without using the global jail_sysvipc_allow ? Cheers, -- Demelier