From owner-freebsd-questions@FreeBSD.ORG Tue Feb 14 21:32:05 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E40DB16A420 for ; Tue, 14 Feb 2006 21:32:05 +0000 (GMT) (envelope-from danielby@slightlystrange.org) Received: from catflap.slightlystrange.org (cpc1-cmbg1-3-0-cust61.cmbg.cable.ntl.com [62.253.132.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB91C43D49 for ; Tue, 14 Feb 2006 21:32:04 +0000 (GMT) (envelope-from danielby@slightlystrange.org) Received: from danielby by catflap.slightlystrange.org with local (Exim 4.60 #0) id 1F97mE-0006vj-Rg by authid for ; Tue, 14 Feb 2006 21:32:02 +0000 Date: Tue, 14 Feb 2006 21:32:02 +0000 From: Daniel Bye To: freebsd-questions@freebsd.org Message-ID: <20060214213202.GA69337@catflap.slightlystrange.org> Mail-Followup-To: freebsd-questions@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: danielby@slightlystrange.org X-SA-Exim-Scanned: No (on catflap.slightlystrange.org); SAEximRunCond expanded to false Subject: Re: Samba port X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Bye List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2006 21:32:06 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 14, 2006 at 03:31:02PM -0500, Ugo Bellavance wrote: > Hi, >=20 > I'm rather new to FreeBSD (I usually use linux and I'm trying Fbsd. I > upgraded my samba port yesterday, but after, I couldn't reconnect to it. > I found out that the upgrade (using cvsup/portupgrade) removed smb.conf > and stopped smb and cups? Why is it this way? It is not the only port > that gets stopped on an upgrade. Is that normal? Shouldn't it at least > try to restart? portupgrade (and portmanager) will try to restart upgraded daemons (smbd, exim, or whatever) in order that they run the new code. As far as I am aware, an upgraded port should not touch an existing config file. Did you upgrade from version 2 to version 3? This might account for it, but I can't remeber if I had similar problems making that particular journey. Anyway, for clues, you can try starting samba directly: # /usr/local/etc/rc.d/samba.sh start and see what debuggibg you get. Welcome to FreeBSD, btw. Hope you stick around! HTH, Dan --=20 Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD8kxShvzwOpChvo8RAm0MAKChcImyU0T1hfb/6aMXoO6R52cQjgCgpSHG /hwtsjKYiT1LXUa1kKFHPIs= =i4ND -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv--