qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: Does anyone actually use -smb
Date: Tue, 05 May 2009 08:18:02 +0200	[thread overview]
Message-ID: <49FFDA1A.6090408@web.de> (raw)
In-Reply-To: <20090505014744.GD12731@shareable.org>

[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]

Jamie Lokier wrote:
> 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 ran strace -e open and only caught this:

[pid 28902] open("/var/log/samba/log.smbd", O_WRONLY|O_CREAT|O_APPEND,
0644) = -1 EACCES (Permission denied)

But that would only be a problem if I ran qemu as root. Hmm, wait, I can
fix it by specifying the file like this:

log file=/tmp/qemu-smb.28902/log.%m

Will write a patch for qemu.

> 
> 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?

OpenSUSE 11.0 with samba-3.2.4-4.3 and 11.1 with samba-3.2.7-11.2.1.

Maybe you should file a bug at your distro if its version doesn't behave
according to its docs.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-05-05  6:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 18:20 [Qemu-devel] Does anyone actually use -smb Anthony Liguori
2009-05-04 20:19 ` [Qemu-devel] " Jan Kiszka
2009-05-04 20:25   ` Jan Kiszka
2009-05-04 21:36   ` Anthony Liguori
2009-05-04 21:40     ` Jan Kiszka
2009-05-05  1:47   ` Jamie Lokier
2009-05-05  6:18     ` Jan Kiszka [this message]
2009-05-05  7:27       ` Jan Kiszka
2009-05-05 12:13         ` Alexey Eremenko
2009-05-05 12:09       ` Jamie Lokier
2009-05-05 13:52         ` Jan Kiszka
2009-05-05 15:07           ` Avi Kivity
2009-05-05 12:10       ` Jamie Lokier
2009-05-05 13:34     ` Anthony Liguori
2009-05-05 13:55       ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49FFDA1A.6090408@web.de \
    --to=jan.kiszka@web.de \
    --cc=aliguori@us.ibm.com \
    --cc=jamie@shareable.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).