From: Michael Tokarev <mjt@tls.msk.ru>
To: 728876@bugs.debian.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Qemu Development List <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Bug#728876: qemu: smbd forked by qemu uses global directory /var/run/samba/ncalrpc
Date: Mon, 07 Apr 2014 14:05:59 +0400 [thread overview]
Message-ID: <53427887.3010407@msgid.tls.msk.ru> (raw)
In-Reply-To: <52F2093E.9050004@msgid.tls.msk.ru>
05.02.2014 13:49, Michael Tokarev wrote:
> Ping? Again, more than 2 months passed since initial submission.
Ping#2 ?
Should it go to -trivial maybe?
Thanks,
/mjt
>
> 29.11.2013 00:15, Michael Tokarev wrote:
>> Jan, there's one more samba-related fix for slirp, also from Michael Büsch.
>>
>> Add my
>>
>> Signed-off-By: Michael Tokarev <mjt@tls.msk.ru>
>>
>> if needed.
>>
>> Thanks,
>>
>> /mjt
>>
>> 06.11.2013 17:01, Michael Büsch wrote:
>>> Package: qemu
>>> Version: 1.6.0+dfsg-2
>>> Severity: normal
>>> Tags: patch
>>>
>>> The smbd forked by qemu still uses the default ncalrpc directory
>>> in /var/run/samba. This may lead to problems, if the directory
>>> does not exist (for example if /var/run is a tmpfs and the host
>>> smbd was not started).
>>>
>>> This leads to the following error message from samba
>>> and an unworkable smbd:
>>> Failed to create pipe directory /var/run/samba/ncalrpc - No such file
>>> or directory
>>>
>>> The attached patch fixes this by pointing smbd to /tmp/qemu-smb.%d.%d/ncalrpc
>>> as ncalrpc directory.
>>> Smbd will create the actual ncalrpc subdirectory on its own.
>>>
>>> Using a private directory also avoids possible clashes with the system-smbd.
>>
>
>
prev parent reply other threads:[~2014-04-07 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131106130127.31489.30934.reportbug@localhost>
2013-11-28 20:15 ` [Qemu-devel] Bug#728876: qemu: smbd forked by qemu uses global directory /var/run/samba/ncalrpc Michael Tokarev
2014-02-05 9:49 ` Michael Tokarev
2014-04-07 10:05 ` Michael Tokarev [this message]
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=53427887.3010407@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=728876@bugs.debian.org \
--cc=Qemu-devel@nongnu.org \
--cc=jan.kiszka@siemens.com \
/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.