s3:lib/messages: use 'msg.lock' and 'msg.sock' for messaging related subdirs
commit1aabd9298d59d4f57d321ecaee59e99d966089ff
authorStefan Metzmacher <metze@samba.org>
Wed, 16 Sep 2015 10:44:43 +0000 (16 12:44 +0200)
committerStefan Metzmacher <metze@samba.org>
Thu, 17 Sep 2015 04:03:17 +0000 (17 06:03 +0200)
treeb165a83f98cd02f6929ca79f1c027e07e843b2de
parentb0fa8316beefc7808b059f514448d41224d1c1fb
s3:lib/messages: 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>
source3/lib/messages.c