On Sun, 2013-04-21 at 14:07 +0200, François Lafont wrote: > Hello, > > Le 20/04/2013 20:00, Michael Wood a écrit : > > > As Andrew suggested it would be good if you could run it under > > valgrind and reproduce the crash. > > I don't know valgrind sorry. In spite of all, I have tried this: > > --------------------------------------------------------------- > apt-get install valgrind > > ./configure --enable-debug #<--- I add the --enable-debug > make > make install > > samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI > --server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123' > echo "nameserver 192.168.0.21" > /etc/resolv.conf > samba > > ln -s /usr/local/samba/lib/libnss_winbind.so /lib/libnss_winbind.so > ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2 > > # I put "winbind" in the nsswitch.conf file. > sed -i -r -e 's/^(passwd:.*)$/\1 winbind/g' -e 's/^(group:.*)$/\1 winbind/g' > /etc/nsswitch.conf > > valgrind --leak-check=full samba -i M single > out 2>&1
Can you try that again with: valgrind samba -i -M single > out 2>&1 I'm not worried about memory leaks (they don't cause crashes), and missing the '-' in front of -M probably means you didn't get the crash in the log you gave. Either way, it's so large I can't make heads or tails of it. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba