Quoting Yuriy Padlyak ([EMAIL PROTECTED]):
> Yes, it is production machine, but I may try lenny package. It is not
> very critical file server and it's well backed up daily :). I'm getting
> these error message few times a day, so I think I'll see if it works
> very quickly.
>
> Can you sug
On Tue, Oct 14, 2008 at 07:08:20AM +0200, Christian Perrier wrote:
> Quoting Steve Langasek ([EMAIL PROTECTED]):
> > There was plenty of information in the original bug report.
> Hmmm, correct, I was missing the original BR.
> The problem happened with 3.0.24 from Etch. I suspect this might be
Christian Perrier написав(ла):
Quoting Steve Langasek ([EMAIL PROTECTED]):
There was plenty of information in the original bug report.
Hmmm, correct, I was missing the original BR.
The problem happened with 3.0.24 from Etch. I suspect this might be on
a production machine where tr
Quoting Steve Langasek ([EMAIL PROTECTED]):
> There was plenty of information in the original bug report.
Hmmm, correct, I was missing the original BR.
The problem happened with 3.0.24 from Etch. I suspect this might be on
a production machine where trying to reproduce it with the version of
s
reopen 501773
thanks
On Mon, Oct 13, 2008 at 06:30:35PM +0200, Christian Perrier wrote:
> > If the problem persists, you are encouraged to first install the
> > samba-dbg package, which contains the debugging symbols for the Samba
> > binaries. Then submit the provided information as a bug repor
Today I got such mail from root, but as I see there are no much details :(
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 4756 (/usr/sbin/smbd).
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated
6 matches
Mail list logo
