From owner-freebsd-gnome@FreeBSD.ORG Mon Dec 14 12:21:31 2009 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56FAA10656A4 for ; Mon, 14 Dec 2009 12:21:31 +0000 (UTC) (envelope-from gesbbb@yahoo.com) Received: from smtp104.prem.mail.ac4.yahoo.com (smtp104.prem.mail.ac4.yahoo.com [76.13.13.43]) by mx1.freebsd.org (Postfix) with SMTP id EF5C38FC0C for ; Mon, 14 Dec 2009 12:21:30 +0000 (UTC) Received: (qmail 72447 invoked from network); 14 Dec 2009 12:21:30 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Received:Date:From:To:Subject:Message-ID:In-Reply-To:References:Followup-To:Reply-To:Organization:X-Mailer:Face:Mime-Version:Content-Type:Content-Transfer-Encoding; b=xouraFhyZID79rg3/jh931il9FLGaVv1hnE/pVF8NWcJbwDGwG7NRi44SJuQDee7MIWHaf5f4ItiCqxlsiFZODsrRfVbJoAmw5Q8oHuM+QqI2kGgvpTX+kNj31DRM5RAKGFNGxBhVWbJPJCdm2SLRWX4wemPHPPRZW0wYGB9L3o= ; Received: from c-67-189-183-172.hsd1.ny.comcast.net (gesbbb@67.189.183.172 with login) by smtp104.prem.mail.ac4.yahoo.com with SMTP; 14 Dec 2009 04:21:29 -0800 PST X-Yahoo-SMTP: yeAAMgKswBATCul4lSbCWspvTA-- X-YMail-OSG: RSZ9mZ8VM1mfSmPNP4.thRn99xESGmFriw4gC7Wgq4Pf4YmBY5iYFjXNj3bGnHeVLHnrHMClt8eEeOS9Q5gT1X_Q4p.sJ93BEEX7EZJMImAtbZXrNhNyH1_yC8YWPQeHZ9XxpKrGXH4GOa8_a3mzgtB1Uc18s54_mH1Ez4sakl0UtkUROyjgKeqiwEaoiSSO0nF9jactgrezBWgBhukfIYD6l8Gc3KT2yuHfp6Wi7RtmOXx.qUm0joBT2u41Iyc_ygnNkDRggXXlIJfYfMvdwLpA.7mVv4iL50llHp59it9RyDw.aCtiHza5y_xu58ROtx00Fr.uYJPWLtYXOkJDFwCj_pISduSTWQr019RifdNjTxDqci7rF.amLoFdHk3_xKHa X-Yahoo-Newman-Property: ymail-3 Received: from scorpio.seibercom.net (scorpio.seibercom.net [192.168.1.101]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: gesbbb@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 94D7C2282C for ; Mon, 14 Dec 2009 07:21:29 -0500 (EST) Date: Mon, 14 Dec 2009 07:21:29 -0500 From: Jerry To: freebsd-gnome@freebsd.org Message-ID: <20091214072129.16b5a5e4@scorpio.seibercom.net> In-Reply-To: <1260791543.2072.25.camel@localhost> References: <20091214060341.0954426c@scorpio.seibercom.net> <1260791543.2072.25.camel@localhost> Followup-To: freebsd-gnome@freebsd.org Organization: seibercom.net X-Mailer: Claws Mail 3.7.3 (GTK+ 2.18.5; i386-portbld-freebsd7.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEX+/v7++v6YOTrq8PCcuIX989UvOSj++v0BNCbpAAAAB3RJTUUHsQwfFzs7RBhzUQAAAhJJREFUOI1dU8GOqzAMNKIoV1bvwD1i0ysqrHplIdBrVSX7ATSbd03VVvn9tQNtQy0hjAdn7LED4AAcPtWm9RV+MPSfxhBLx9ajd6X/ngB6/mTwnRSZua7i7Ca+0ctZKo4Qmz+JY13X6I3nFZBxIYW1PbgfQ5RP8g0XlltEWGf3cV03joYpRnFbvYDKbXjZlXyyhEZA4lI+cN3NaVXE4VKjSwTExO10eTEkkJVqIAD5z0nUBQJluQDRSQjcrBiHAJxZlAH5CUMBMC7OcJ4LMQNnxhZ1HYPscMc6J4UlWRMNwzOpCcAHKSICd1EDn83abdREIbXsHkD1OinP1aCUCOEVRaa1lMcvywUWdYgk13JQUpYNKmvXQ8Kw5ML9YI5h8SakctBc7E/IYuLhYd/zZIk+1gM1vNweQBvHE0j+oYah3sMqAytQYlZk6+ANaaawJdu3OFzYGMZ3iGpa3qMlq9ZH0VZTgrCtw/ngdYkEIIpSbP1bWQAdFdX9vocBdkH2qVjVmuMu3gI5rjs814EUdrCZgWlPaxZZ3RiLFUtr+ud0PXwp2dnQSNXgePt6AZpBj6UMJ7VQkzN4utVeaSW1Dhn/kblGrKeMvNGnzwX4zuEDarYz1KdPtR60Gul0Gued+515SJXhCsl+Tx/3kY/UDvicPll9mfu50t3tvQ/thZpJYgeuwdSKNJ6tCD98MCgoxLDaPxbwqqwPWaWiAAAAAElFTkSuQmCC X-Face: "\j?x](l|]4p?-1Bf@!wN<&p=$.}^k-HgL}cJKbQZ3r#Ar]\%U(#6}'?<3s7%(%(gxJxxcR Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: thanks for nothing on the Samba 4 upgrade X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-gnome@freebsd.org List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 12:21:31 -0000 On Mon, 14 Dec 2009 14:52:23 +0300 Vladimir Grebenschikov articulated: > Hi > > Me too! > > samba4-devel is required for mail/evolution-mapi samba3 and samba4 > can't coexist on single installation without special tweaks. > > for me, "it does not works" means: > > 1. samba4 complains about many configuration values in old smb.conf > > $ smbclient > Unknown parameter encountered: "guest account" > Ignoring unknown parameter "guest account" > Unknown parameter encountered: "max log size" > Ignoring unknown parameter "max log size" > Unknown parameter encountered: "map to guest" > Ignoring unknown parameter "map to guest" > ... etc > $ > > (have fixed this manually) > > 2. It is impossible to login with old credentials that worked > correctly with samba3 to server. Looks like it is due to complete > change of auth core of samba. > > 3. I've failed to re-configure samba4 to enable any logins (using > samba4 site as guide), it fails with coredumps and such: > > # /usr/local/share/samba4/setup/provision --realm myrealm > --domain=vbook --adminpass=password --server-role='standalone' > --setupdir=/usr/local/share/samba4/setup Setting up secrets.ldb > Setting up the registry Setting up templates db > Setting up idmap db > schema_fsmo_init: no schema head present: (skip schema loading) > naming_fsmo_init: no partitions dn present: (skip loading of naming > contexts details) pdc_fsmo_init: no domain object present: (skip > loading of domain details) schema_fsmo_init: no schema dn present: > (skip schema loading) naming_fsmo_init: no partitions dn present: > (skip loading of naming contexts details) pdc_fsmo_init: no domain dn > present: (skip loading of domain details) Setting up sam.ldb > attributes Setting up sam.ldb rootDSE > Erasing data from partitions > schema_fsmo_init: no schema head present: (skip schema loading) > naming_fsmo_init: no partitions dn present: (skip loading of naming > contexts details) pdc_fsmo_init: no domain object present: (skip > loading of domain details) Pre-loading the Samba 4 and AD schema > Segmentation fault (core dumped) > # > > upgrade script does not works also: > > # /usr/local/share/samba4/setup/upgrade > --setupdir /usr/local/share/samba4/setup --realm > myrealm /usr/local/etc/samba/ /usr/local/etc/smb.conf.v3 Traceback > (most recent call last): File > "/usr/local/share/samba4/setup/upgrade", line 66, in samba3 > = Samba3(libdir, smbconf) File > "/usr/local/lib/python2.6/site-packages/samba/samba3.py", line 741, > in __init__ self.lp.read(self.smbconfpath) File > "/usr/local/lib/python2.6/site-packages/samba/samba3.py", line 695, > in read raise Error("Unable to parser line %d: %r" % (i+1,l)) > NameError: global name 'Error' is not defined # > > > -----Original Message----- > From: Jerry > Reply-to: freebsd-gnome@freebsd.org > To: freebsd-gnome@freebsd.org > Subject: Re: thanks for nothing on the Samba 4 upgrade > Date: Mon, 14 Dec 2009 06:03:41 -0500 > > On Sun, 13 Dec 2009 23:13:02 -0800 > paul beard articulated: > > > Not sure why samba 4 is required for evolution-data-server but > > installing it breaks my minimal but functional samba install. Sounds > > like a POLA violation to me. The various provisioning and upgrade > > scripts don't seem to work. I'm dropping back to samba 3 to see if I > > can nurse it back to something workable. > > > > Sorry to see that you are experiencing difficulties. However, a simple > post: "It doesn't work" is simply useless. Could you please supply a > detailed log, examples, smb.conf file, etc. Then and only then would > someone be able to possibly assist you. > OK, while I am not using evolution or the latest Samba version, I do have a friend who is, using samba4-devel that is. I just contacted them and they said that what you are experiencing is not the norm. They suggested the following. 1) Completely remove all versions of Samba currently on your system. Something like: pkg_delete -dfv samba* That should remove all remnants of Samba from your system. You may have to manually remove, or at least rename the smb.conf file. If there is a stale start up file in the 'rc.d' directory, remove it. Either delete or move all of the files in the '/var/log/samba' directory. You want fresh output. Now, do a clean install of "samba4-devel-4.0.0.a8_2". Be sure to run 'make config' first to insure you have it configured the way you want. Next, config Samba using any method you prefer. Personally, I like using SWAT; however, that is up to you. Now use the start up script to start the program. You might want to do a reboot to insure it starts correctly on start up. If you are still experiencing difficulties, try posting to the Samba forum and contacting "timur@FreeBSD.org" the Samba port maintainer. -- Jerry gesbbb@yahoo.com |::::======= |::::======= |=========== |=========== | All the passions make us commit faults; love makes us commit the most ridiculous ones. La Rochefoucauld