From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] slirp-smb broken with Samba 4.1
Date: Fri, 24 Oct 2014 23:58:37 +0400 [thread overview]
Message-ID: <544AAF6D.2060101@msgid.tls.msk.ru> (raw)
In-Reply-To: <544A9A6E.9080700@msgid.tls.msk.ru>
On 10/24/2014 10:29 PM, Michael Tokarev wrote:
> On 10/24/2014 08:55 PM, Jan Kiszka wrote:
>> Hi Michael,
>>
>> writing to you as you provided a fix for the last related issue:
>>
>> I just noticed that the samba-based share is broken again with smbd
>> version 4.1.11. Tried to look briefly at it, realized that it is a
>> permission thing (different error when qemu runs as root) but also some
>> more nasty problem with configuring r/w guest access to a share. If you
>> have experience in that area, maybe you have an idea.
>
> Oh well.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747636#15 -- note the
> date. I don't know if that my old analisys is correct and whenever
> anything has changed since that time...
Actually it seems wrong.
My 4.1.11 version tries to open /var/log/samba/log.smbd.bin file and
gives up. After I created that file and chowned it to me it works.
I'm trying to find out what tells smbd to use that .bin file...
What error are you getting when run it as root?
/mjt
next prev parent reply other threads:[~2014-10-24 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 16:55 [Qemu-devel] slirp-smb broken with Samba 4.1 Jan Kiszka
2014-10-24 18:29 ` Michael Tokarev
2014-10-24 19:58 ` Michael Tokarev [this message]
2014-10-24 20:43 ` Michael Tokarev
2014-10-25 7:23 ` Jan Kiszka
2014-11-03 12:22 ` Peter Wu
2014-11-03 12:58 ` Michael Tokarev
2014-11-03 19:46 ` [Qemu-devel] Improved shared folders support (was: Re: slirp-smb broken with Samba 4.1) Peter Wu
2014-11-04 6:13 ` [Qemu-devel] Improved shared folders support Michael Tokarev
2014-11-05 17:29 ` Peter Wu
2014-11-04 22:53 ` [Qemu-devel] slirp-smb broken with Samba 4.1 Peter Wu
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=544AAF6D.2060101@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=jan.kiszka@siemens.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.