freebsd stable - Oct 2009 - security.bsd.map_at_zero=0 problem with samba33 (including solution)

FYI,

after setting security.bsd.map_at_zero to 0 on 7.2-STABLE all
samba33 programmes did abort() immediately after start. The
solution was to use

CONFIGURE_ARGS+= --disable-pie

	-Andre

-- 
BSD, from the people who brought you TCP/IP.

On Sat, 3 Oct 2009 14:42 -0000, Andre.Albsmeier wrote:
> FYI,
>
> after setting security.bsd.map_at_zero to 0 on 7.2-STABLE all
> samba33 programmes did abort() immediately after start. The
> solution was to use
>
> CONFIGURE_ARGS+= --disable-pie
>
> 	-Andre
>
To add an additional note samba33 even when not running (not enabled by a rcvar)
also runs a tdbcleanup routine on shutdown and/or start that also does 
abort().


-- 

%{----------------------------------------------------+
  | dataix.net!jhell         2048R/89D8547E 2009-09-30 |
  | BSD since FreeBSD 4.2    Linux since Slackware 2.1 |
  | 85EF E26B 07BB 3777 76BE  B12A 9057 8789 89D8 547E |
  +----------------------------------------------------%}

On Sat, 03-Oct-2009 at 16:27:32 -0400, jhell wrote:
> On Sat, 3 Oct 2009 14:42 -0000, Andre.Albsmeier wrote:
> 
> > FYI,
> >
> > after setting security.bsd.map_at_zero to 0 on 7.2-STABLE all
> > samba33 programmes did abort() immediately after start. The
> > solution was to use
> >
> > CONFIGURE_ARGS+= --disable-pie
> >
> > 	-Andre
> >
> 
> To add an additional note samba33 even when not running (not enabled by a
rcvar)
> also runs a tdbcleanup routine on shutdown and/or start that also does 
> abort().
Yes, every samba programme is linked with -pie per default (so
all abort()).

	-Andre