From owner-freebsd-current Tue Nov 3 18:27:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29236 for freebsd-current-outgoing; Tue, 3 Nov 1998 18:27:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-15.dialip.mich.net [192.195.231.217]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA29231 for ; Tue, 3 Nov 1998 18:27:23 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811040227.SAA29231@hub.freebsd.org> Received: (qmail 1297 invoked from smtpd); 4 Nov 1998 02:28:15 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 4 Nov 1998 02:28:15 -0000 Date: Tue, 3 Nov 1998 21:28:14 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: samba smbd core dumps & -current To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm having problems with smbd coredumping on -current (as of a week ago or so)... this has been happening for a while. i've upgraded to samba1.9.18p10 to no avail. it seems to happen whenever a user authenticates to it; guest access seems to work okay. strange thing it is... any tips? i haven't seen any discussion of this on here... same configuration as before: pentiumII/300, aout system, 96MB of ram, no problems with smbd before recent -current's. if nobody else has seen this, i'll compile with debugging information and attempt to track this thing down. btw- the inetd patch has kept inetd from dying so far, thankfully. it would have died by now without it. enjoy -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... for the stupid-patent-of-the-week: Whois: JAG145 "...an attache case with destruct means for destroying the contents therein in response to a signal" -- patent no. US3643609, filed in 1969 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message