LogoopenSUSE Build Service > Projects
Sign Up | Log In

View File Fix-run-lock-directories-permissions-to-follow-openSUSE-po.patch of Package systemd (Project Base:System)

From: Frederic Crozat <fcrozat@suse.com>
Date: Wed, 7 Dec 2011 15:15:07 +0000
Subject: Fix /run/lock directories permissions to follow openSUSE policy

disable /var/lock/{subsys,lockdev} and change default permissions on
/var/lock (bnc#733523).
---
 tmpfiles.d/legacy.conf |    7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

Index: systemd-221/tmpfiles.d/legacy.conf
===================================================================
--- systemd-221.orig/tmpfiles.d/legacy.conf
+++ systemd-221/tmpfiles.d/legacy.conf
@@ -10,13 +10,14 @@
 # These files are considered legacy and are unnecessary on legacy-free
 # systems.
 
-d /run/lock 0755 root root -
+# changed for openSUSE: only /run/lock should be available.
+d /run/lock 0775 root lock -
 L /var/lock - - - - ../run/lock
 
 # /run/lock/subsys is used for serializing SysV service execution, and
 # hence without use on SysV-less systems.
 
-d /run/lock/subsys 0755 root root -
+#d /run/lock/subsys 0755 root root -
 
 # /run/lock/lockdev is used to serialize access to tty devices via
 # LCK..xxx style lock files, For more information see:
@@ -24,7 +25,7 @@ d /run/lock/subsys 0755 root root -
 # On modern systems a BSD file lock is a better choice if
 # serialization is needed on those devices.
 
-d /run/lock/lockdev 0775 root lock -
+#d /run/lock/lockdev 0775 root lock -
 
 # /forcefsck, /fastboot and /forcequotacheck are deprecated in favor of the
 # kernel command line options 'fsck.mode=force', 'fsck.mode=skip' and