security.bsd.map_at_zero=0 problem with samba33 (including solution)

[Andre Albsmeier]

On Sat, 03-Oct-2009 at 22:27:39 +0000, Bjoern A. Zeeb wrote:
> On Sat, 3 Oct 2009, Andre Albsmeier wrote:
> 
> Hi,
> 
> > 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()).
> 
> 
> Thanks for reporting the issue.  People are aware of the problem now
> and we'll try to present a solution within the next days for better
> position-independent executable (PIE) handling.
> 
> Meanwhile there are multiple solutions for people affected:
> 
> (1) recompile the port; but as more than just samba might be affected
>      and we generally do not want to flip the pie switch everywhere that's
> probably only a temporary, private solution.

I'll stick to this since I am happy about having the map_at_zero
option and want to continue to try it out on 7.2-STABLE. And I
see now reason why samba has to be linked with -pie (without -pie
it is also 4% smaller).

	-Andre

-- 
"I think there is a world market for maybe five computers."
                     - Thomas Watson, chairman of IBM, 1943