** Patch added: smb-patch.diff
https://bugs.launchpad.net/bugs/988125/+attachment/3102872/+files/smb-patch.diff
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/988125
Title:
Generated smb.conf
Public bug reported:
The smb.conf generated by the userspace networking does not include a state
directory
directive. Samba therefore falls back to the default value. Since the user
generally
does not have write access to this path, smbd immediately crashes.
I have attached a patch that adds
** Patch added: Previous patch was broken
https://bugs.launchpad.net/qemu/+bug/988125/+attachment/3102896/+files/smb-patch.diff
** Patch removed: smb-patch.diff
https://bugs.launchpad.net/qemu/+bug/988125/+attachment/3102872/+files/smb-patch.diff
--
You received this bug notification
Public bug reported:
The smb.conf generated by qemu-kvm contains a smb ports = 0 directive. This
causes at least version 3.6.4 of Samba to crash with
[0] vostro:/tmp/qemu-smb.6836-0# smbd -i -s smb.conf
Unable to setup corepath for smbd: Operation not permitted
smbd version 3.6.4 started.
(commit
http://gitweb.samba.org/?p=samba.git;a=commit;h=7b02e05eb64f3ffd7aa1cf027d10a7343c0da757).
This patch adds the missing option.
Signed-off-by: Nikolaus Rath nikol...@rath.org
---
diff -r -u qemu-kvm-1.0.1.old/net/slirp.c qemu-kvm-1.0.1/net/slirp.c
--- qemu-kvm-1.0.1.old/net/slirp.c 2012-04
This option is available since 3.4.0.
I just sent a patch to qemu-devel. Am I going to get some confirmation
when it is applied? I'm unfamiliar with the development model.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
-by: Nikolaus Rath nikol...@rath.org
diff -u -r qemu-kvm-1.0+dfsg.old/net/slirp.c qemu-kvm-1.0+dfsg/net/slirp.c
--- qemu-kvm-1.0+dfsg.old/net/slirp.c 2011-12-04 05:38:06.0 -0500
+++ qemu-kvm-1.0+dfsg/net/slirp.c 2012-04-25 14:40:39.859737798 -0400
@@ -507,7 +507,6 @@
fprintf(f
qemu-devel mail:
http://article.gmane.org/gmane.comp.emulators.qemu/148378
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/988125
Title:
Generated smb.conf needs to declare state directory
Status
Sent a patch to qemu-devel,
http://article.gmane.org/gmane.comp.emulators.qemu/148378
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/988128
Title:
smbd crashes when called with smb ports = 0
Wrong link, sorry. This is the right one:
http://article.gmane.org/gmane.comp.emulators.qemu/148286/
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/988125
Title:
Generated smb.conf needs to declare
Hi,
It'd be great if someone could take a look at this and apply it if there
are no objections...
Thanks,
-Nikolaus
Nikolaus Rath nikol...@rath.org writes:
The smb.conf generated by the userspace networking does not include a state
directory
directive. Samba therefore falls back
Nikolaus Rath nikol...@rath.org writes:
Hello,
The smb ports = 0 option causes recent samba versions to crash. It was
introduced in commit 15ef3e with log message Samba 3 support.
However, a value of 0 has never been officially supported by smb and is
also not necessary: if stdin is a socket
Thanks a lot Peter! I can confirm that this patch fixes the problems
when added on top of Debian's qemu-kvm 1.1.2+dfsg-4 package. I have
attached a patch against the Debian git tree.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
** Patch added: Patch against debian package
https://bugs.launchpad.net/qemu/+bug/1033727/+attachment/3482404/+files/qemu-debian.diff
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1033727
Title:
14 matches
Mail list logo
