Start a Conversation

Unsolved

7

3 Posts

764

January 27th, 2021 08:00

Running shell script on Wyse ThinLinux 5070 from WMS.

Hello - Is it possible to download & run a shell script on a Wyse ThinLinux 5070 from the Wyse Management Suite?  The Wyse ThinLinux 5070 is registered with the WMS & can be rebooted, etc. via the WMS console.  We're using WMS 1.4 with ThinLinux 2.2.  Any suggestions or links to tutorials/examples would be most welcome.  Thanks.

3 Posts

January 28th, 2021 13:00

Brief update: We've upgraded to WMS 3.1 which according to page 63 of the admin guide supports script deployment.

PG 63

Important notes for Linux devices:

  • Supports script deployments for ThinLinux devices with extensions .sh. 

Also, here:

https://www.technicalhelp.de/2020/12/03/wyse-management-suite-3-1-release/

Scripting support for Advanced App policy – This feature is enabled on ThinLinux 2.x. Bash script support .sh(bash), with command-line argument support to Advanced App Policies for ThinLinux. Script Type supported: .sh(bash), .py(python) and .pl(pearl).

When I look at the ThinLinux Advanced App policy panel, I see a number of blank lines labeled Line 1, etc.  Are there any examples shell command syntax?  I have a shell script we need to deploy, do I copy it line for line? 

Any insights would be much appreciated.

3 Posts

February 1st, 2021 11:00

In a nutshell: the script appears to be pushed to the ThinLinux device where it attempts to execute but fails.  Some details:
 
We have updated the ThinLinux OS & the WDA is the latest (3.5.1-13) as recommended.  I am testing using a simple script (hola.sh):
cd /home/thinuser/Downloads
echo "Hola ThinLinux!" > tt
Since the job shows error in WMS after running, I explicitly set the exit code on a version of the test shell (hola0.sh):
cd /home/thinuser/Downloads
echo "Hola ThinLinux!" > tt
exit 0
 
This script should change to the Downloads directory & write a small file with the line " Hola ThinLinux!".
 
The App Policy is added using the "Add Advanced Policy" button with the groups, ThinLinux, script, etc. specified.
 
The job shows as running in the WMS & the thin client prompts to start the job.  After starting the job on the thin client, the screen changes to aqua blue with words to the effect: don't shut off power.  It returns to the normal thin client console quickly.  There is no small test file present anywhere on the harddrive.
 
The WMS shows the following after the job finishes:
hola-thinlinux‎02‎/‎01‎/‎21 ‎6‎:‎38‎:‎34‎ ‎PM plum-thin-linux App Policy Scheduler  Error ‎02‎/‎01‎/‎21 ‎6‎:‎39‎:‎34‎ ‎PMSuccess: 0,    Pending: 0,    In-Progress: 0
Delayed: 0,    Failed:  1,    Canceled
No Events found!

Top