jhell writes:
Hi,
This was caused by your setting of the following:
security.bsd.map_at_zero=0
You can reset that value to 1 and you should be alright to operate like
normal otherwise you will have to compile samba over again with the above
mentioned configure options.
Yeah this
On Thu, 8 Oct 2009, Oliver Lehmann wrote:
This was caused by your setting of the following:
security.bsd.map_at_zero=0 You can reset that value to 1 and you should be
alright to operate like normal otherwise you will have to compile samba
over again with the above mentioned configure
On Thu, 8 Oct 2009, Robert Watson wrote:
On Thu, 8 Oct 2009, Oliver Lehmann wrote:
This was caused by your setting of the following:
security.bsd.map_at_zero=0 You can reset that value to 1 and you should be
alright to operate like normal otherwise you will have to compile samba
over again
On Thu, 8 Oct 2009, Daniel Eischen wrote:
While it's probably a bug that the Samba port compiles --pie, it's also a
bug that our linking bits aren't handling PIE properly either. The goal is
to fix PIE with the non-NULL mapping feature in the immediate future, so
with any luck the abort
Hi,
I wonder what may have caused this and how should I debug it to find the
source? I Installed samba 3.3.7 on a clean 8.0-RC1 and I upgraded then my
system to the latest RELENG_8.
Since I've not the time searching much longer for the error I'll just go
to upgrade to 3.3.8 (recompile it...)
On Wed, 7 Oct 2009 20:09 +0200, lehmann@ wrote:
Hi,
I wonder what may have caused this and how should I debug it to find the
source? I Installed samba 3.3.7 on a clean 8.0-RC1 and I upgraded then my
system to the latest RELENG_8.
Since I've not the time searching much longer for the error I'll
On Wednesday 07 October 2009 20:09:59 Oliver Lehmann wrote:
Hi,
I wonder what may have caused this and how should I debug it to find the
source? I Installed samba 3.3.7 on a clean 8.0-RC1 and I upgraded then my
system to the latest RELENG_8.
Since I've not the time searching much longer for
