Re: incompatible screen update

2011-02-13 Thread Lennart Poettering
On Thu, 10.02.11 09:33, Miroslav Lichvar (mlich...@redhat.com) wrote: On Tue, Feb 08, 2011 at 06:16:29PM +0100, Lennart Poettering wrote: The problem is it would require making screen setuid root which I do not think it is too good idea. Well, I think the fear of making something

Re: incompatible screen update

2011-02-10 Thread Miroslav Lichvar
On Tue, Feb 08, 2011 at 06:16:29PM +0100, Lennart Poettering wrote: The problem is it would require making screen setuid root which I do not think it is too good idea. Well, I think the fear of making something SUID root is not reason enough not to make things technically correct. How

Re: incompatible screen update

2011-02-09 Thread Nicolas Mailhot
Le Mar 8 février 2011 08:42, Lennart Poettering a écrit : On Fri, 04.02.11 16:30, Miroslav Lichvar (mlich...@redhat.com) wrote: Hi, just a heads up, the screen package in rawhide was updated to a pre 4.1.0 git snapshot and after the update you won't be able to reattach to your old screen

Re: incompatible screen update

2011-02-09 Thread Nicolas Mailhot
Le Mar 8 février 2011 15:05, Tomas Mraz a écrit : I think much more reasonable is to just accept the fact that it might be very reasonable and desirable on some multiuser system to allow users having background processes that can keep running even after the user logs out and not to try to

Re: incompatible screen update

2011-02-09 Thread Lennart Poettering
On Wed, 09.02.11 10:33, Nicolas Mailhot (nicolas.mail...@laposte.net) wrote: Le Mar 8 février 2011 15:05, Tomas Mraz a écrit : I think much more reasonable is to just accept the fact that it might be very reasonable and desirable on some multiuser system to allow users having

Re: incompatible screen update

2011-02-09 Thread Nicolas Mailhot
Le Mer 9 février 2011 10:33, Nicolas Mailhot a écrit : It's kind of ironic that our main UI (gnome3) is changing to be more video-appliance-like, but at the same time we've been killing all the bits like background processes that would have made it a good appliance fit (see also freedombox).

Re: incompatible screen update

2011-02-09 Thread Ben Boeckel
Lennart Poettering mzerq...@0pointer.de wrote: Fact is that people have been requesting the ability to have guaranteed clean-up of processes on logout, and we do provide this now (though only opt-in) with systemd. If this is enabled this currently breaks screen. And I think it would make sense

Re: incompatible screen update

2011-02-08 Thread Miroslav Lichvar
On Tue, Feb 08, 2011 at 08:42:52AM +0100, Lennart Poettering wrote: On Fri, 04.02.11 16:30, Miroslav Lichvar (mlich...@redhat.com) wrote: - $HOME/.screen is used as socket directory instead of /var/run/screen $HOME is no place to place unix sockets. Unfortunately $HOME might be one

Re: incompatible screen update

2011-02-08 Thread Lennart Poettering
On Tue, 08.02.11 12:09, Miroslav Lichvar (mlich...@redhat.com) wrote: On Tue, Feb 08, 2011 at 08:42:52AM +0100, Lennart Poettering wrote: On Fri, 04.02.11 16:30, Miroslav Lichvar (mlich...@redhat.com) wrote: - $HOME/.screen is used as socket directory instead of /var/run/screen

Re: incompatible screen update

2011-02-08 Thread Tomas Mraz
On Tue, 2011-02-08 at 12:40 +0100, Lennart Poettering wrote: On Tue, 08.02.11 12:09, Miroslav Lichvar (mlich...@redhat.com) wrote: On Tue, Feb 08, 2011 at 08:42:52AM +0100, Lennart Poettering wrote: On Fri, 04.02.11 16:30, Miroslav Lichvar (mlich...@redhat.com) wrote: -

Re: incompatible screen update

2011-02-08 Thread Martin Dengler
On Tue, Feb 08, 2011 at 03:05:03PM +0100, Tomas Mraz wrote: [Let's] not to try to enforce rules such as no user process left after logout blindly on all systems. Not that I disagree with your statement (I tend to agree) in general, but how is screen is running but detached morally equivalent to

Re: incompatible screen update

2011-02-08 Thread Tomas Mraz
On Tue, 2011-02-08 at 14:28 +, Martin Dengler wrote: On Tue, Feb 08, 2011 at 03:05:03PM +0100, Tomas Mraz wrote: [Let's] not to try to enforce rules such as no user process left after logout blindly on all systems. Not that I disagree with your statement (I tend to agree) in general,

Re: incompatible screen update

2011-02-08 Thread Martin Dengler
O n Tue, Feb 08, 2011 at 03:33:08PM +0100, Tomas Mraz wrote: On Tue, 2011-02-08 at 14:28 +, Martin Dengler wrote: On Tue, Feb 08, 2011 at 03:05:03PM +0100, Tomas Mraz wrote: [Let's] not to try to enforce rules such as no user process left after logout blindly on all systems. Not

Re: incompatible screen update

2011-02-08 Thread Lennart Poettering
On Tue, 08.02.11 15:05, Tomas Mraz (tm...@redhat.com) wrote: Precisely for issues like this XDG_RUNTIME_DIR has recently been introduced: http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html We carefully made sure to define the semantics of this dir to offer a

Re: incompatible screen update

2011-02-07 Thread Lennart Poettering
On Fri, 04.02.11 16:30, Miroslav Lichvar (mlich...@redhat.com) wrote: Hi, just a heads up, the screen package in rawhide was updated to a pre 4.1.0 git snapshot and after the update you won't be able to reattach to your old screen session. There are actually three incompatible changes:

incompatible screen update

2011-02-04 Thread Miroslav Lichvar
Hi, just a heads up, the screen package in rawhide was updated to a pre 4.1.0 git snapshot and after the update you won't be able to reattach to your old screen session. There are actually three incompatible changes: - the change in screen protocol - $HOME/.screen is used as socket directory