[openthinclient-user] cron/at job

2011-11-17 Thread Stefan Vater
hi otc expterts,

i've a question:

i want to auto shutdown my otc clients in the evening (as my users are
to lazy or stu to do so).
bit as i see it, there is no crond or atd in otc ?!

is there an other possibility to get this done?


regards,
stefan

--
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
The Open Source Thin Client Solution http://openthinclient.org
openthinclient-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openthinclient-user


Re: [openthinclient-user] cron/at job

2011-11-17 Thread Gary Horneman
Hi,
I have worked on this same issue for several years and finally have an
answer that works.

Create a command line application with the following command line

echo 0pen%TC | sudo -S  shutdown -P -h 18:00 Scheduled 6:00 pm shutdown

Set it to Autostart. Assoicate the application with the thinclient.

Of course you will change the shutdown time to whatever time would like.

Some history.
Shutdown must be executed by an administrator of the system. That is why
the sudo is needed.
In the past, while I could shut down the thinclient using this command (on
OTC 0.4.5), the NIC was not correctly conditioned on most of my clients for
WOL (wake-on-LAN)  to work. In fact for some of them, I had to pull the
power cord in order to start up successfully. People on this list pointed
me to the ethtool which did allow the NIC to be correctly conditioned. At
this point, I got stuck because while I could figure out the correct
ethtool command line, I couldn't get it executed.
In 0.4.5, more than one autostart (sudo?) command line application caused
all of them to fail. (I have not tried this on OTC 1.0) I tried various
combinations of multiple commands in one line but couldn't get it to work.
I had a few other options to try but never got around to them.
With OTC 1.0, it correctly conditions all my NICs - even the ones that I
used to have to pull the power cord on, so I only need the single autostart
application to shut down the client. I then have a scheduled task on a
windows server that issues the WOL in the morning.

It would be nice if autoshutdown was a configurable item for a client but I
am happy with this solution for now.
On Thu, Nov 17, 2011 at 5:44 AM, Stefan Vater s...@gmx.net wrote:

 hi otc expterts,

 i've a question:

 i want to auto shutdown my otc clients in the evening (as my users are
 to lazy or stu to do so).
 bit as i see it, there is no crond or atd in otc ?!

 is there an other possibility to get this done?


 regards,
 stefan


 --
 All the data continuously generated in your IT infrastructure
 contains a definitive record of customers, application performance,
 security threats, fraudulent activity, and more. Splunk takes this
 data and makes sense of it. IT sense. And common sense.
 http://p.sf.net/sfu/splunk-novd2d
 ___
 The Open Source Thin Client Solution http://openthinclient.org
 openthinclient-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/openthinclient-user




-- 
Gary Horneman
Technology Director
Rosary High School
630 896-0831 x27
--
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d___
The Open Source Thin Client Solution http://openthinclient.org
openthinclient-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openthinclient-user