From owner-freebsd-current Fri Apr 17 01:19:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04304 for freebsd-current-outgoing; Fri, 17 Apr 1998 01:19:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04287 for ; Fri, 17 Apr 1998 08:19:17 GMT (envelope-from kpielorz@caladan.tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.8.8/8.8.8) with SMTP id JAA04707 for ; Fri, 17 Apr 1998 09:19:15 +0100 (BST) (envelope-from kpielorz@caladan.tdx.co.uk) Date: Fri, 17 Apr 1998 09:19:15 +0100 (BST) From: Karl Pielorz To: current@FreeBSD.ORG Subject: Problems with 3.0-980311-SNAP & Samba 1.9.18p4 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've just installed 3.0-980311-SNAP on my system... It's the first time I've been running a 3.0 system as my 'main' (but not mission critical) machine... Everything went very smoothly - except Samba now refuses to work... If I boot the system back off it's old 2.2.6 drive it works fine (with either samba 1.9.18p3 or p4) - but with the new system under the 3.0 SNAP I get: Apr 17 08:57:26 caladan /kernel: pid 4664 (smbd), uid 2000: exited on signal 8 The samba logs don't show anything 'going wrong' even with debug level 9 set... :-( I've also made sure that the 3.0 system is a 'pure' system (i.e. theres no old 2.2.6 binaries / libs kicking around) - in fact it's guarenteed 100% pure as it's on a new disk, and the old one is disconnected! And my other machine (an NT box) gives "An unexpected network error has occured" (10 out of 10 for the nice cryptic NT error ;-) I'm kinda new to actually doing anything with 3.0-CURRENT my original plan was to run a SNAP for a few months - and then upgrade as and when... I'm looking at setting up cvsup etc. to at least keep the source on the system current... Is it a good idea for me just to grab -the latest- source and do a makeworld - is this the only likely thing that's going to stand a chance of fixing samba? Is there any documentation anywhere I can look at with a view of going through the nice .core files it produced and trying to find out what went wrong? Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message