[arch-dev-public] WARNING: changes to screen in testing
When you run with systemd's default tmpfiles configuration and you use screen, your screen sockets are deleted after 10 days. This is bad and caused me some trouble. I changed screen in testing to use /run/screens instead, which won't be cleared by tmpfiles - and it is the correct place for this stuff anyway. However, when upgrading the screen package, your existing screens will become unaccessible. How should we handle this?
On Mon, Oct 22, 2012 at 08:00:18PM +0200, Thomas Bächler wrote:
When you run with systemd's default tmpfiles configuration and you use screen, your screen sockets are deleted after 10 days. This is bad and caused me some trouble.
I changed screen in testing to use /run/screens instead, which won't be cleared by tmpfiles - and it is the correct place for this stuff anyway.
Bleh, XDG_RUNTIME_DIR would a be a better place, but sadly this isn't going to exist for some population of users.
However, when upgrading the screen package, your existing screens will become unaccessible. How should we handle this?
Surely there's a way to tell screen to look in a different place for sockets. Figure out the command to do so and advertise it in a post_upgrade message as a crutch until the user can restart their screen sessions. d
Am 22.10.2012 20:13, schrieb Dave Reisner:
On Mon, Oct 22, 2012 at 08:00:18PM +0200, Thomas Bächler wrote:
When you run with systemd's default tmpfiles configuration and you use screen, your screen sockets are deleted after 10 days. This is bad and caused me some trouble.
I changed screen in testing to use /run/screens instead, which won't be cleared by tmpfiles - and it is the correct place for this stuff anyway.
Bleh, XDG_RUNTIME_DIR would a be a better place, but sadly this isn't going to exist for some population of users.
For the multi-user features of screen to work, you need to store all screen sockets in one place.
On 10/22/12, Thomas Bächler <thomas@archlinux.org> wrote:
However, when upgrading the screen package, your existing screens will become unaccessible. How should we handle this?
Something similar happened on a debian system I administer. Their solution was to have a special temporary binary for connecting to the old session. Maybe a preinstall hook that copies the old screen binary to /tmp? -Kyle http://kmkeen.com
Am 22.10.2012 20:00, schrieb Thomas Bächler:
When you run with systemd's default tmpfiles configuration and you use screen, your screen sockets are deleted after 10 days. This is bad and caused me some trouble.
I changed screen in testing to use /run/screens instead, which won't be cleared by tmpfiles - and it is the correct place for this stuff anyway.
However, when upgrading the screen package, your existing screens will become unaccessible. How should we handle this?
Okay, finally pushed a new version with a helpful post_install message. I'll move this to extra later unless someone objects.
participants (3)
-
Dave Reisner
-
keenerd
-
Thomas Bächler