From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M19lC-0002Fk-42
	for qemu-devel@nongnu.org; Mon, 04 May 2009 21:47:54 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M19l7-0002Ev-Gz
	for qemu-devel@nongnu.org; Mon, 04 May 2009 21:47:53 -0400
Received: from [199.232.76.173] (port=33950 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M19l7-0002Es-Bm
	for qemu-devel@nongnu.org; Mon, 04 May 2009 21:47:49 -0400
Received: from mail2.shareable.org ([80.68.89.115]:35190)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1M19l6-0006p2-OG
	for qemu-devel@nongnu.org; Mon, 04 May 2009 21:47:49 -0400
Date: Tue, 5 May 2009 02:47:44 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Re: Does anyone actually use -smb
Message-ID: <20090505014744.GD12731@shareable.org>
References: <49FF31E4.8040106@us.ibm.com> <49FF4DC2.4020003@web.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <49FF4DC2.4020003@web.de>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

Jan Kiszka wrote:
> Anthony Liguori wrote:
> > It looks to be broken.  I don't recall that Samba has every supported
> > running as an unprivileged user to so it would require launching as root.
> 
> It works perfectly. I even have a patch pending that fixes the zombie
> issue it causes (more precisely, slirp missed that).

I've been unable to use it for a year or so due to Samba having
hard-coded directory paths, pointing into /var/lib/samba, which cannot
be overridden in the config file smb.conf.

(I forget which files were hard-coded, or which distro I hit that on.
Either CentOS, Debian or Ubuntu.  Files were something like
/var/lib/samba/{locking,connections}.tdb, perhaps?)

Because of those paths, non-root wasn't possible and running it as
root caused it to try to clobber some files which interfered with a
non-QEMU ("native") Samba running on the same machine for normal file
service.

I guess if you have a private build of Samba you can avoid this
problem, but even then I'm wondering how you ensure different Samba
instances don't interfere with each other, as there is nowhere in
smb.conf to specify an alternate location for those files normally in
/var/lib/samba.

Jan, do you do anything special for -smb or does it just work?  What
distro and distro version are you using?

Thanks,
-- Jamie