Your message dated Sun, 5 Mar 2017 18:07:22 +0100
with message-id <[email protected]>
and subject line screen 4.5.1-1 from Debian Experimental uses libutempter
instead of setgid utmp, hence all /var/run/screen permission problems should be
gone
has caused the Debian Bug report #471763,
regarding my /var/run/screen is owned by a different group than utmp, so I get
"Directory '/var/run/screen' must have mode 777" at startup
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.)
--
471763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471763
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: screen
Version: 4.0.3-13
Severity: minor
Tags: patch
Thanks for maintaining screen.
== My problem ==
Whenever I try to start screen, I get the error message "Directory
'/var/run/screen' must have mode 777". /usr/bin/screen is owned by
0(root):43(utmp). But /var/run/screen is owned by 0(root):22(voice).
I have no idea why.
If I chmod 777 /var/run/screen, it fixes the problem. Alternatively,
if I chown root:utmp /var/run/screen, it also fixes the problem.
My /var/log/dpkg.log{,*gz} files are incomplete but they show that
some of the screen versions I've ever used include 4.0.2.4-1,
4.0.3-0.2, 4.0.3-0.3+b1, 4.0.3-11, and 4.0.3-13.
Bug http://bugs.debian.org/471763 describes a couple of different
problems. My problem is very similar to Ambrose Li's and Stephen
Kitt's. Mine is not very similar to Daniel Dickinson's.
== Suggested fix ==
In message http://bugs.debian.org/471763#45 Daniel Hornung suggests
that if you swap lines 25 and 26 of /etc/init.d/screen-cleanup, it
will fix my problem. I have attached a patch which swaps those two
lines. Why not apply it?
--- screen-cleanup 2009-06-21 04:04:05.000000000 +0000
+++ screen-cleanup.new 2009-06-21 04:04:37.000000000 +0000
@@ -22,8 +22,8 @@
if test -L $SCREENDIR || ! test -d $SCREENDIR; then
rm -f $SCREENDIR
mkdir $SCREENDIR
- chown root:utmp $SCREENDIR
fi
+ chown root:utmp $SCREENDIR
find $SCREENDIR -type p -print0 | xargs -0r rm -f --
# If the local admin has used dpkg-statoverride to install the screen
# binary with different set[ug]id bits, change the permissions of
--- End Message ---
--- Begin Message ---
Version: 4.5.1-1
Hi,
yesterday, I've uploaded screen 4.5.1-1 to Debian Experimental. It
uses libutempter instead of setgid utmp, hence all /var/run/screen
permission problems should be gone.
Hence closing these two bug reports.
Feel free to reopen them in case the issue still pops up with screen
4.5.1-1 or later.
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--- End Message ---
