s4:lib/messaging: use 'msg.lock' and 'msg.sock' for messaging related subdirs
authorStefan Metzmacher <metze@samba.org>
Wed, 16 Sep 2015 10:44:43 +0000 (12:44 +0200)
committerStefan Metzmacher <metze@samba.org>
Thu, 17 Sep 2015 07:04:59 +0000 (09:04 +0200)
commit1d2a1a685ebdf479c511e01764e5148dbcbb37c9
tree871f934cb48d873a56b1f92798c7ae83d7c06538
parent1aabd9298d59d4f57d321ecaee59e99d966089ff
s4:lib/messaging: use 'msg.lock' and 'msg.sock' for messaging related subdirs

In Samba 4.2, we used lock_path("msg") (with 0700) for the socket directory,
while we use lock_path("msg") (with 0755) for the lock file directory.

This generates a conflict that prevents samba, smbd, nmbd and winbindd
from starting after an upgrade.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=11515

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Volker Lendecke <vl@samba.org>
Autobuild-User(master): Stefan Metzmacher <metze@samba.org>
Autobuild-Date(master): Thu Sep 17 09:04:59 CEST 2015 on sn-devel-104
source4/lib/messaging/messaging.c