On 13.10 my dmesg is still full of winbind output. Output of dmesg |
grep winbind:
[ 38.614222] init: winbind main process (1566) terminated with status 127
[ 38.614249] init: winbind main process ended, respawning
[ 38.637502] init: winbind main process (1569) terminated with status 127
[
I used to solved the problem by adding the following, in the smb.conf
server services = +smb -s3fs
dcerpc endpoint servers = +winreg +srvsvc
thanks to Iain by pointing out
https://wiki.samba.org/index.php/Samba4/Releases/4.0.0beta2
by the way I used to upgrade samba 3.3.10 to
See comment #7 - apparent trivial package screwup
** Changed in: samba4 (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055075
Title:
samba4 default
Hi Jelmer, I ran into this issue as well, it appears that in the current
13.04 version the 11_force_ntvfs is in debian/patches but missing from
debian/patches/series. Fix is trivial, I'm happy to attach it if that
helps.
--
You received this bug notification because you are a member of Ubuntu
I get the same issue. According to this:
https://wiki.samba.org/index.php/Samba4/Releases/4.0.0beta2
smbd is now the default, but ntvfs can be used.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694697
There was a similar bug reported here (guess this is what this package is based
on?)
Did you provision this server? It seems like it still has the old
configuration.
You'll also need to enable the ntvfs file server.
** Changed in: samba4 (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Observation; In the boot logs I see:
[ 11.335866] init: winbind main process (2135) terminated with status 127
[ 11.335884] init: winbind main process ended, respawning
[ 11.338729] init: winbind main process (2139) terminated with status 127
[ 11.338745] init: winbind main process ended,
** Attachment added: smb.conf
https://bugs.launchpad.net/bugs/1055075/+attachment/3335233/+files/smb.conf
** Tags added: apport-collected
** Description changed:
I installed samba4, added a share /test to smb.conf and tried to access it
and got
$ smbclient -L localhost -U%
Connection
Confirmed: I could recreate this
Medium: This is the universe version of samba not the main one; and also if
this is just a default config problem then it's not a high; although I don't
know enough Samba to know if it's really more serious.
I suspect there are multiple bugs here; the log.%m
