Your message dated Sat, 13 Oct 2018 15:55:00 +0100
with message-id <[email protected]>
and subject line Re: RE: Bug#687202: initscripts: /run/lock has perms 0755
instead of 1777
has caused the Debian Bug report #687202,
regarding initscripts: /run/lock has perms 0755 instead of 1777
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
687202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687202
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initscripts
Version: 2.88dsf-31
Severity: important
Dear Maintainer,
/run/lock is created with perms 0755 in /lib/init/mount-functions.sh :
mount_lock().
This prevents non-privileged users from creating files/directories in /run/lock.
In particular, the logcheck package runs as a logcheck user and fails to create
/run/lock/logcheck.
Changing mount_lock() to mkdir with --mode=1777 fixes the problem.
-- System Information:
Debian Release: wheezy/sid
Architecture: armhf (armv6l)
Kernel: Linux 3.2.27+ (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages initscripts depends on:
ii coreutils 8.13-3.2
ii debianutils 4.3.2
ii libc6 2.13-35
ii lsb-base 4.1+Debian7
ii sysv-rc 2.88dsf-31
ii sysvinit-utils 2.88dsf-31
Versions of packages initscripts recommends:
ii e2fsprogs 1.42.5-1
ii psmisc 22.19-1
initscripts suggests no packages.
-- Configuration Files:
/etc/default/tmpfs changed:
LOCK_MODE=1777 #ineffective
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 14 Sep 2012 17:37:44 +0100 "'Alan Dennis'"
<[email protected]> wrote:
> Hi,
>
> Sorry, but I think this might not actually be an initscripts bug after all.
> I'm also using flashybrid and in my mind I'd eliminated that as the source
> of the problem, but I disabled it just to double check and when rebooted,
> /run/lock had the correct permissions. I suspect that flashybrid can't cope
> with /run in some way - I'll get back to you with more information when/if
> I've figured out what's happening.
Closing the bug since this never happened.
Ben.
--
Ben Hutchings
All the simple programs have been written, and all the good names taken
signature.asc
Description: This is a digitally signed message part
--- End Message ---
