On Mon, Jan 26, 2004 at 10:54:32PM -0600, tvsjr wrote:
> At 02:41 PM 01/26/2004 -0800, Mike Fedyk wrote:
> >I ran the same 3.0.1-2-debug1 under valgrind to get this output.
> >
> >I only ran it for a short period of time because samba is giving access
> >denied errors that it doesn't when not being
At 02:41 PM 01/26/2004 -0800, Mike Fedyk wrote:
>I ran the same 3.0.1-2-debug1 under valgrind to get this output.
>
>I only ran it for a short period of time because samba is giving access
>denied errors that it doesn't when not being traced by valgrind. It's
>probably some interaction with nss-ld
On Thu, Jan 22, 2004 at 08:19:19PM -0800, Mike Fedyk wrote:
> Got one! (This is after switching back to a 2.4 kernel -- I was on 2.6.1 for
> the last week or so, and that was the entire time I had the debugging
> version of samba runing too, so there's some kind of "child exiting before
> parent no
On Fri, Jan 23, 2004 at 06:10:35PM +1100, Andrew Bartlett wrote:
> On Fri, 2004-01-23 at 15:19, Mike Fedyk wrote:
> > Hmm, do I need to compile my libc non-stripped, or is the problem in
> > tdb/tdb.c:1498?
> >
>
> It's not there. it's somewhere else - set MALLOC_CHECK_=2 into your
> environment
On Fri, 2004-01-23 at 15:19, Mike Fedyk wrote:
> On Thu, Jan 22, 2004 at 03:02:59PM -0800, Mike Fedyk wrote:
> > On Thu, Jan 22, 2004 at 12:16:29PM -0800, Mike Fedyk wrote:
> > > I have a custom smb.conf file which I'm attaching, and have just added:
> > >
> > > panic action = "/usr/share/samba/pa
On Thu, Jan 22, 2004 at 03:02:59PM -0800, Mike Fedyk wrote:
> On Thu, Jan 22, 2004 at 12:16:29PM -0800, Mike Fedyk wrote:
> > I have a custom smb.conf file which I'm attaching, and have just added:
> >
> > panic action = "/usr/share/samba/panic-action"
>
> Well, I figured out it should have been
On Thu, Jan 22, 2004 at 12:16:29PM -0800, Mike Fedyk wrote:
> I have a custom smb.conf file which I'm attaching, and have just added:
>
> panic action = "/usr/share/samba/panic-action"
Well, I figured out it should have been
panic action = "/usr/share/samba/panic-action %d"
But unfortunately I
On Wed, Jan 21, 2004 at 02:05:42PM -0600, Steve Langasek wrote:
> Mike,
>
> On Wed, Jan 21, 2004 at 11:29:33AM -0800, Mike Fedyk wrote:
> > On Wed, Jan 21, 2004 at 11:10:40AM -0800, Mike Fedyk wrote:
> > > I'm still looking through my logs to see if there are any new traces there.
>
> > All clien
Mike,
On Wed, Jan 21, 2004 at 11:29:33AM -0800, Mike Fedyk wrote:
> On Wed, Jan 21, 2004 at 11:10:40AM -0800, Mike Fedyk wrote:
> > I'm still looking through my logs to see if there are any new traces there.
> All clients are win2k, except for scitex which is win98.
> And here are some more:
Ba
On Wed, Jan 21, 2004 at 11:10:40AM -0800, Mike Fedyk wrote:
> I'm still looking through my logs to see if there are any new traces there.
All clients are win2k, except for scitex which is win98.
And here are some more:
comp.team-c-jhernand-[2004/01/20 16:15:29, 0] lib/util.c:smb_panic(1408)
comp
BACKTRACE: 3 stack frames:
#0 /usr/sbin/smbd(smb_panic+0x101) [0x81bdcb1]
#1 /usr/sbin/smbd [0x81ac097]
#2 [0xe420]
I've been getting a lot of these now that I have the non-stripped version of
samba running.
I'm still looking through my logs to see if there are any new traces there
On Fri, Jan 16, 2004 at 04:54:12PM -0800, Mike Fedyk wrote:
> On Wed, Nov 05, 2003 at 06:15:47PM -0600, Steve Langasek wrote:
> > Ok, then, you *must* build debugging-enabled packages by running... :)
> >
> > The binaries are compiled with debugging turned on -- the debugging
> > symbols are strip
12 matches
Mail list logo
