Re: Way to auto-set all users' screens to NOT go idle/lock?

Hello Alkis, Rolf and Dashamir,

Thanks for your replies.

Alkis' your solution works great, Thanks! Your explanation helps me
consider my classroom computer setup (I hadn't clearly separated concepts
of 'client' and 'user'!):

> LTSP does not handle *user* settings.
> It only handles *client* settings.
>
and:

> Dconf settings for all users are described in
> https://wiki.gnome.org/Projects/dconf/SystemAdministrators
> GNOME, MATE and many other DEs use dconf for their settings.
>

Rolf, we have used the lts.conf setting: "X_BLANKING=0" for a few years and
it really is great so the displays don't sleep. In our situation, while the
display wouldn't sleep, it would still be inaccessible due to login issue
(though I understand you were giving it as a separate solution). Your
further elaboration of what Alkis had suggested helped me understanding
that option better, thanks.

Dashamir, indeed that was my concern, too, thus I wasn't looking for a
solution to that problem but am glad to see it. Also, your comment that
Alkis' solution was a common one surprised me and I wondered why I didn't
see it in the lts.conf manpage when I looked. So I went back and sure
enough it was there, and sure enough I had seen/read it but I hadn't
recognize it as the solution!

*LDM_PASSWORD_HASH*
           boolean, default *False*

           When set to *True*, this will create a proper shadow entry
on the client, allowing for
           screen locking, and other things which require
authentication to work. Note, this
           allows you to change your password locally, or possibly
other actions such as sudo,
           but these changes are only temporary and will not persist on reboot.

May I suggest a change/addition something like,
"...allowing for screen locking, [that is, with this option set to True,
the user will be able to authenticate and re-enter their session when the
screen is locked. This also allows those] other things which require
authentication to work"
This would help those of us who know something but are still learning some
of the basics.

Cheers,
David

On Thu, Jan 10, 2019 at 6:54 AM Dashamir Hoxha <[email protected]> wrote:

> On Thu, Jan 10, 2019 at 11:22 AM Rolf-Werner Eilert <[email protected]>
> wrote:
>
>> Am 10.01.19 um 03:13 schrieb David Groos:
>> > Hello,
>> >
>> > The following screenshot shows how users prefs are automatically set:
>> > https://pasteboard.co/HVJeUSi.png that is:
>> > 1.  "Regard the computer as idle after:" 30 minutes,
>> > 2.  "Activate screenshaver when computer is idle"
>> > 3.  "Lock screen when screensaver is active"
>> >
>>
>> For point 3, use Alkis' solution LDM_PASSWORD_HASH=True. We use it very
>> successfully. It does not deactivate the screensaver, but you are able
>> to logon again.
>>
>
> This is the common solution, but David mentioned that they use Active
> Directory
> for authentication. This makes it a special case. It would be great if
> this solution
> works for Active Directory authentication too. I am curious to know, and
> hopefully
> David will try it out and let us know whether it works or not.
>
> Regards,
> Dashamir
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>       https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net
>

_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net