/var/run/samba/ntp_signd and /var/run/samba/winbindd are not created automatically when running samba4. After Creating them manually Samba4 runs OK.
Do you run s4 at least once with the "root" account? Since only then we have the permission to create these two folders and the sockets in it. Another problem could be that the path specified on "configure" and the installation path afterwards don't match. Then please perform a full rebuild ("make clean", "configure", "make"...) I mark this as "INVALID" since this isn't a bug (tested on my computer).
(In reply to comment #1) > Do you run s4 at least once with the "root" account? Since only then we have > the permission to create these two folders and the sockets in it. Another > problem could be that the path specified on "configure" and the installation > path afterwards don't match. Then please perform a full rebuild ("make clean", > "configure", "make"...) > > I mark this as "INVALID" since this isn't a bug (tested on my computer). >
Even when running first time with root, the dirs are not created I used Debian Lenny. With a pre-packed deb pkg using jelmer work, of the latest git from today 11/04/2010 Sassy
Matthias, /var/run can exist (In reply to comment #1) > Do you run s4 at least once with the "root" account? Since only then we have > the permission to create these two folders and the sockets in it. Another > problem could be that the path specified on "configure" and the installation > path afterwards don't match. Then please perform a full rebuild ("make clean", > "configure", "make"...) > > I mark this as "INVALID" since this isn't a bug (tested on my computer). just because you can't reproduce it doesn't mean it's not a bug... /var/run can be on a tmpfs, in which case these directories disappear after each reboot. Arguably creating these directories could also be done in the init script on D
Arguably these directories could also be created by the init script, but since they are configurable in smb.conf that is a bit tricky. It would be much simpler if samba could take care of creating them.
Natan, sorry I closed the bug due to a misconception. You speak from the "PID" files under "var/run" I however controlled the socket files and directories under "var/lib" (and these work). I will talk to someone about fixing this (I think the bug shows up only on FHS installations and therefore was undiscovered 'till now).
This could have been fixed by http://gitweb.samba.org/samba.git/?p=samba.git;a=commitdiff;h=7233699ad849b0771c946eb47b31ff50f64cefbf. Please rebuild using WAF and retest!
No, I still need to do a mkdir -p /var/run/samba
isnt' it a pb of the init script ?
Arguably this should be done by the init script, and this is what happens on Debian/Ubuntu these days.