I've had the same problem with Debian Lenny, when I compile latest Samba packet
(3.4.5).
But, I've resolved this adding repositories testing in my sources.list.
After, I install Samba with apt-get.
--
Luiz Gustavo P Tonello.
On Jan 25, 2010, at 11:26 PM, Jeremy Allison wrote:
On Mon,
Am 2010-01-26 10:53, schrieb Luiz Gustavo P Tonello:
I've had the same problem with Debian Lenny, when I compile latest Samba packet
(3.4.5).
But, I've resolved this adding repositories testing in my sources.list.
After, I install Samba with apt-get.
--
Luiz Gustavo P Tonello.
Mhmm,
On Tue, Jan 26, 2010 at 10:58:05AM +0100, Martin Hochreiter wrote:
Am 2010-01-26 10:53, schrieb Luiz Gustavo P Tonello:
I've had the same problem with Debian Lenny, when I compile latest Samba
packet (3.4.5).
But, I've resolved this adding repositories testing in my sources.list.
After,
I have libkerb53 and libkerb5-dev (V. 1.6)
--
Luiz Gustavo P Tonello.
On Jan 26, 2010, at 7:58 AM, Martin Hochreiter wrote:
Am 2010-01-26 10:53, schrieb Luiz Gustavo P Tonello:
I've had the same problem with Debian Lenny, when I compile latest Samba
packet (3.4.5).
But, I've resolved
BTW, can you upload a debug level 10 log for this crash?
Maybe we can figure out what is happening from there, if
valgrind or a gdb backtrace are impossible.
Thanks,
Volker
Yes, I will do that around lunchtime - valgrind and debug symbols
are complete new worlds for a simple sysadmin
BTW, can you upload a debug level 10 log for this crash?
Maybe we can figure out what is happening from there, if
valgrind or a gdb backtrace are impossible.
Thanks,
Volker
Shame on me, but I don't get along with that -
I let the 3.4.5 samba running for 5 minutes on debug level 1
and had a
On Tue, Jan 26, 2010 at 01:15:05PM +0100, Martin Hochreiter wrote:
BTW, can you upload a debug level 10 log for this crash?
Maybe we can figure out what is happening from there, if
valgrind or a gdb backtrace are impossible.
Thanks,
Volker
Shame on me, but I don't get along with that
Am 2010-01-26 13:49, schrieb Volker Lendecke:
Maybe they just did not happen? Or maybe they are rotated
away quickly? Maybe you want to set max log size larger
for a while?
Volker
quick and simple - you where soo right!
I let samba run for about an hour and have the information -
I
On Mon, Jan 25, 2010 at 03:25:46PM +0100, Martin Hochreiter wrote:
I recently installed Samba 3.4.5 on Ubuntu 8.04 64 bit and
had to downgrad again because of massive core panics:
Can you try to reproduce that under valgrind?
Thanks,
Volker
--
To unsubscribe from this list go to the
Am 2010-01-25 15:41, schrieb Volker Lendecke:
On Mon, Jan 25, 2010 at 03:25:46PM +0100, Martin Hochreiter wrote:
I recently installed Samba 3.4.5 on Ubuntu 8.04 64 bit and
had to downgrad again because of massive core panics:
Can you try to reproduce that under valgrind?
On Mon, Jan 25, 2010 at 03:53:07PM +0100, Martin Hochreiter wrote:
Am 2010-01-25 15:41, schrieb Volker Lendecke:
On Mon, Jan 25, 2010 at 03:25:46PM +0100, Martin Hochreiter wrote:
I recently installed Samba 3.4.5 on Ubuntu 8.04 64 bit and
had to downgrad again because of massive core
On Mon, Jan 25, 2010 at 03:25:46PM +0100, Martin Hochreiter wrote:
I recently installed Samba 3.4.5 on Ubuntu 8.04 64 bit and
had to downgrad again because of massive core panics:
I can't really tell you what caused that (maybe while printing via
samba-cups) - can
somebody give me a hint
Can you install the debug symbols, and try and
reproduce the problem please ? Open a bug at bugzilla.samba.org
and add the line:
panic action = /bin/sleep 9
to the [global] section of your smb.conf. Once the crash
re-occurs, attach to the parent process of the sleep using
gdb, and then
13 matches
Mail list logo
