Date: Sun, 31 May 2009 17:49:23 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@zabbadoz.net> To: Boris Samorodov <bsam@ipt.ru> Cc: freebsd-jail@FreeBSD.org Subject: Re: sysvipc in jails + CURRENT Message-ID: <20090531174837.R3234@maildrop.int.zabbadoz.net> In-Reply-To: <11979393@h30.sp.ipt.ru> References: <11979393@h30.sp.ipt.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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/messages > May 31 18:22:47 pg postgres[55425]: [1-1] FATAL: could not create shared memory segment: Function not implemented > May 31 18:22:47 pg postgres[55425]: [1-2] DETAIL: Failed system call was shmget(key=5432001, size=30384128, 03600). > % sysctl security.jail.sysvipc_allowed > security.jail.sysvipc_allowed: 0 > % grep sysvipc /etc/sysctl.conf > security.jail.sysvipc_allowed=1 > ----- the host ----- > % uname -a > FreeBSD tba.bsam.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun May 31 11:28:31 MSD 2009 root@tba.bsam.ru:/usr/obj/usr/src/sys/TBA amd64 > % sysctl security.jail.sysvipc_allowed > security.jail.sysvipc_allowed: 1 > ----- I'll look into that; possibly the default option is not properly taken into account for the new jail framework. /bz -- Bjoern A. Zeeb The greatest risk is not taking one.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090531174837.R3234>