Your message dated Sun, 29 Apr 2012 18:00:09 +0100
with message-id <[email protected]>
and subject line Re: Bug#637856: /run/lock should be owned by uucp
has caused the Debian Bug report #637856,
regarding /run/lock should be owned by uucp
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.)
--
637856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637856
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initscripts
Version: 2.88dsf-13.11
Hi,
there are programs that stat() /var/lock to test permissions
instead of actually trying to create lockfiles, the java rxtx
library for example. Before making this symlink to the /run/lock
tmpfs, ownership was preserved on harddisk.
A simple chgrp uucp /run/lock || true after creation/mounting of
/run/lock solves this and does not hurt programmes just trying to
write the lockfile.
A more general apporach is also welcome.
Bye,
Joerg
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Tue, Aug 16, 2011 at 08:53:24AM +0200, Joerg Dorchain wrote:
> On Mon, Aug 15, 2011 at 02:59:04PM +0100, Roger Leigh wrote:
> > I don't think this is an issue restricted to Debian--it is presumably
> > already broken on most other distributions as well? This isn't a
> > recent change, or a change made in isolation. AFAICT it was made
> > for FHS compliance reasons--nowadays /var/lock is used for a lot
> > more than just uucp, so expecting it to be owned by the uucp group
> > is, I think, unrealistic. root:root or root:lock are the way things
> > have gone.
>
> I use this application roughly every other week, on a machine
> following testing, so I am quite sure the change happend in the
> last few weeks.
>
> As said, root:lock ownership with group-write permissions is
> probably ok.
> > We don't currently permit changing of the ownership; the permissions
> > are entirely configurable in /etc/fstab. You could use the tmpfs
> > uid= and gid=options to set the uucp group there.
>
> Thanks for that hint.
Given that the above is a sufficient workaround for the problem,
I'm closing this bug. (We can't change the defaults of the entire
distribution just for the sake a single broken bit of software.
Changing it would break even more programs in any case.)
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
