On Sun, Dec 12, 2010 at 11:32:06AM -0000, Wim Muskee wrote:
> Okay, that worked, i've created a start_screen() in ltsp-init-common,
> which can be called from the Gentoo initscript. Compared to the code in
> ltsp-core, I'm not iterating the 01-12 to actually start
> $SCREEN_DEFAULT, we know it's value already.
it needs to start all of the defined SCREEN_NN entries, otherwise it breaks
multiple screen scripts; only the screen script that ends up being
SCREEN_DEFAULT will get started. if a user switches to another tty, nothing
will happen.
i just committed to bzr moving the code from ltsp-core to a
start_screen_sessions function in ltsp-init-common. let us know if that doesn't
work for gentoo, or if there are changes other distros would need to make it
work.
On Sun, Dec 12, 2010 at 11:32:06AM -0000, Wim Muskee wrote:
> Okay, that worked, i've created a start_screen() in ltsp-init-common,
> which can be called from the Gentoo initscript. Compared to the code in
> ltsp-core, I'm not iterating the 01-12 to actually start
> $SCREEN_DEFAULT, we know it's value already.
it needs to start all of the defined SCREEN_NN entries, otherwise it breaks
multiple screen scripts; only the screen script that ends up being
SCREEN_DEFAULT will get started. if a user switches to another tty, nothing
will happen.
i just committed to bzr moving the code from ltsp-core to a sessions function in ltsp-init-common. let us know if that doesn't
start_screen_
work for gentoo, or if there are changes other distros would need to make it
work.
live well,
vagrant