Follow up on this. I have SAMBA_3_0 from CVS, checked out about 4 days
ago (last time we discussed this). I have been able to cause hte
problem, or another similar problem, im not sure, to be reproduced.
What I was doing was adding a new printer, by editing smb.conf, adding
the new printer entry,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jerry Haltom wrote:
|
| Could a corrupt .tdb of any sort be causing this? It
| is touching a variable named pdb (maybe printer db?),
| but I'm not sure what that is.
It could I guess, but I agree with Jeremy. That's a
strange place to crash. How many
Nope. In fact, I do suspect bad ram. I don't know why it would be
consistant though. I would think that bad ram would effect more than
just samba's printing. And you'd think reacreating the process
(different location in memory) would get around it. The problem is
pretty consistant, it's happening
On Thu, Feb 05, 2004 at 11:29:16AM -0600, Jerry Haltom wrote:
Nope. In fact, I do suspect bad ram. I don't know why it would be
consistant though. I would think that bad ram would effect more than
just samba's printing. And you'd think reacreating the process
(different location in memory)
On Wed, Feb 04, 2004 at 05:35:11PM -0600, Jerry Haltom wrote:
Our computers in our office ceased being able to print to a shared cups
printer today. Could not find the cause. Seems the smbd processes are
dying. Below is the stack trace produced by gdb bt full.
The Samba 'panic action'
I don't know enough about what is going on to know if what I'm saying
makes any sense. :) But I'm working on it.
Could a corrupt .tdb of any sort be causing this? It is touching a
variable named pdb (maybe printer db?), but I'm not sure what that is.
Since I had the problem I have deleted all of
