removed / removido.
http://www.opensubscriber.com/message/ltsp-discuss@lists.sourceforge.net/13836375.html
http://www.k12ltsp.org/mediawiki/index.php/Technical:RemoteClientShutdown
2010/4/23 Ezequiel Coser ezequ...@solis.coop.br
Ltsp5 installed on ubuntu 8.04, but I found that I have not
Ltsp5
installed on ubuntu 8.04, but I found that I have not found the command
ltspinfo.
Is ltspinfo part of LTSP5?
How can I get this command?
--
Ezequiel Coser
Analista de rede/servidores
GNU/Linux User 456470
SOLIS Cooperativa de Solues Livres
www.solis.coop.br
le père Léon a écrit :
Launching ltspinfo -h my_host gives me no result,
wheras nmap -p 9200 my_host says the port is open.
In fact, ltspinfod process is running on the clients.
With ALLOW_SHUTDOWN = Y option in the lts.conf file, I can halt
clients with ltspinfo -h my_host --shutdown.
I've
I continue answering myself, hoping it can help anyone else on the list..
Launching ltspinfo -h my_host gives me no result,
wheras nmap -p 9200 my_host says the port is open.
ltspinfo requires on command
no command = no result
I've also tried ltspinfo -c all -h my_hosts, but it's not easy to
I do NOT know what's going on.
Next time it is better idea to ask @ ltsp forum. (Ill get this
message, but if u want much, CC it to me)
What I found on google as workaround:
https://wiki.ubuntu.com/LTSPClientShutdownReboot
I have an odd experience where I can wake up a client (HP t5125) via
ether-wake at the initial power connection or after pulling the power
and reconnecting, however if I shut it down from the server via
ltspinfo -h workstation -s it does not respond to ether-wake.
I'm running ltsp-4.2.
Hello *.
I have a question about ltspinfo.
Where is the information that it returns read from on the client? Is
the information stored in environmental variables or read from a file
somewhere?
My reason for asking is that I'm thinking of using ltspinfo to return
some dynamic client
Pete,
Take a look at /opt/ltsp/i386/etc/ltsp_functions
the reg_info() function takes care of writing info out to
/tmp/info/${VAR} on the workstation. That's where ltspinfod gets
the value from.
Currently, only some things are being exported that way, for ltspinfod
to get. I'd like to change
John,
Thanks, I'll take it out of the next release of the readme.
Jim McQuillan
[EMAIL PROTECTED]
On Tue, 15 Mar 2005, John Horne wrote:
On Fri, 2005-03-04 at 13:28 -0500, Jim McQuillan wrote:
As for variables missing from /tmp/info, only variables that the client
cares about are put
John-
This looks to be a bug in the way ltspinfo does the reporting on the config..
Jim-
I have been getting this also. on every setting. It looks like
ltspinfo is appending LTSP_ to the start of the variables that it is
reporting.
Evan
On Thu, 03 Mar 2005 16:36:41 +, John Horne
John-
Are you having trouble with a client? If so try replacing that
runlevel with SCREEN_01= startx. On LSTP 4.1 SCREEN_XX replaced
RUNLEVEL.
Evan
On Fri, 4 Mar 2005 10:58:13 -0600, Evan Hisey [EMAIL PROTECTED] wrote:
John-
This looks to be a bug in the way ltspinfo does the reporting on
Evan and John,
It's not a bug, it's a feature.
The idea is that you run ltspinfo like this:
eval `ltspinfo -h ws001 -c ALL`
and it will set the values in your environment.
It prepends 'LTSP_' on the front of all of the variables, so that we
don't step on other variables that might already
Jim-
Okay, makes sense. I'll add that to the ltspinfo wiki page.
Evan
On Fri, 4 Mar 2005 13:28:55 -0500 (EST), Jim McQuillan [EMAIL PROTECTED]
wrote:
Evan and John,
It's not a bug, it's a feature.
The idea is that you run ltspinfo like this:
eval `ltspinfo -h ws001 -c ALL`
Hello,
I having been using ltspinfo to check on a client. In the lts.conf file
I have set the RUNLEVEL value, but ltspinfo does not return a value for
it:
ltspinfo --host 141.163.60.56 --cfg RUNLEVEL
export LTSP_RUNLEVEL=
It seems that ltspinfod uses the /tmp/info directory on the
14 matches
Mail list logo
