Re: Shutdown clients by cronjob

Valtteri Suojanen <[email protected]>
Newsgroups gmane.linux.terminal-server.general
Message-ID <[email protected]>
hi

one approach could be that you find a crontab setup in client system to 
send LTSP clients 'uptime' every 15-30 minutes to some configuration 
that detects from the uptime message  how much/where the average load is 
and decides from the load information and message interval when it's 
safe time to kill/shutdown the client. this can be very difficult to 
configure and adjust just with the uptime. it might be better if reading 
the idle state somewhere from x11 (mouse movement, display, keyboard).

i think also parsing such idle information messages from client should 
be in the server configuration with some service rules. the rules parse 
the client messages indicating the need to shutdown idle clients

to your question I wish you find a way to solve your client problem

Valtteri


Rolf-Werner Eilert kirjoitti 5.2.2019 klo 18.18:
> Just an idea... Is it possible to have clients shutdown by some cronjob?
>
> This might be good to avoid them being brutally disconnected from 
> mains by someone who just switches off the tables or lab and doesn't 
> care.
>
> Is there a way to find out how long a client has been idle?
>
> Or is there at least a way to find out that a client is on and idle?
>
> Regards
> Rolf
>
>
> _____________________________________________________________________
> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.