I did it using Andrew Tridgell's tserver. It is a tiny web server that
has some powerful capabilities.
I documented it on
http://wiki.ltsp.org/twiki/bin/view/Ltsp/ClientWebserver a couple of
years ago
The files size is 15k stripped and just links against libc.
It executes shell commands as
Robin Bonin wrote:
Running LTSP 5 on ubuntu, I need to be able to remote reboot the clients
(I have some clients inside the ceiling driving some monitors with
company stats on them). Ltspinfo seems like it is the right answer in
4.1, but I cant find it on my system. Is there anything else,
Sherwood Botsford wrote:
Why are you reluctant to run ssh?
The biggest problem with running sshd on the thin client is mainly
a performance issue: if you've got 1ghz clients with goodly amount
of ram, yeah, it's a great solution. Problem is, we've got a lot
of people running some really low
Le lundi 27 août 2007 à 13:22 -0500, Scott Balneaves a écrit :
The biggest problem with running sshd on the thin client is mainly
a performance issue: if you've got 1ghz clients with goodly amount
of ram, yeah, it's a great solution. Problem is, we've got a lot
of people running some really
Jean-Michel Dault wrote:
Le lundi 27 août 2007 à 13:22 -0500, Scott Balneaves a écrit :
The biggest problem with running sshd on the thin client is mainly
a performance issue: if you've got 1ghz clients with goodly amount
of ram, yeah, it's a great solution. Problem is, we've got a lot
of
On Mon, Aug 27, 2007 at 01:22:02PM -0500, Scott Balneaves wrote:
Sherwood Botsford wrote:
Why are you reluctant to run ssh?
The biggest problem with running sshd on the thin client is mainly
a performance issue: if you've got 1ghz clients with goodly amount
of ram, yeah, it's a great
Le lundi 27 août 2007 à 15:19 -0500, Scott Balneaves a écrit :
Don't forget that you can run ssh under inetd/xinetd, which means that,
until there's a connection, you don't use any resources.
Good point, we'd have to do some fancy footwork for a few things:
1) We don't want a static
1) We don't want a static inetd.conf, as if no printer's defined
for a terminal, there's no point in starting jetpipe at all. So,
what we'd want to do, on boot, is zero out the inetd.conf file, and
then update-inetd calls based on things like if PRINTER_0_DEV/PORT
are set, LOCALDEV=true are
On Thursday 23 August 2007 19:11:03 Robin Bonin wrote:
Running LTSP 5 on ubuntu, I need to be able to remote reboot the clients
(I have some clients inside the ceiling driving some monitors with
company stats on them). Ltspinfo seems like it is the right answer in
4.1, but I cant find it on my
Running LTSP 5 on ubuntu, I need to be able to remote reboot the clients
(I have some clients inside the ceiling driving some monitors with
company stats on them). Ltspinfo seems like it is the right answer in
4.1, but I cant find it on my system. Is there anything else, other than
running a ssh
10 matches
Mail list logo
