Differences

This shows you the differences between two versions of the page.

--- services:labtest:start [2025/10/24 09:16] – jas
+++ services:labtest:start [2026/08/21 15:30] (current) – jas
@@ Line 146: / Line 146: @@
 <code>
 Labtest (7777A) [labtest1] > help
+Available commands:
 status                                       Display labtest status
@@ Line 164: / Line 166: @@
 quit                                         Quit
+app help                                     Display app help options
+eecsvm help                                  Display eecsvm help options
 lock help                                    Display lock help options
 ltinit help                                  Display ltinit help options
@@ Line 182: / Line 186: @@
   * You can use the "restore" command to restore student files should they forget to submit.
-There are also a few subcommands in Labtest Assistant - lock, ltinit, restrict, and submit which will be described below.
+There are various subcommands in Labtest Assistant - app, eecsvm, lock, ltinit, restrict, and submit, which will be described below.
+===== Labtest Applications Help =====
+<code>
+Labtest (7777A) [labtest1] > app help
+Labtest Application Dock Help:
+In labtest mode, you can specify which applications are available on the app dock at the bottom of the
+screen.
+These applications are ALWAYS included no matter what your settings: Firefox, Logout, and LTRestore
+In labtest lock mode, no additional applications are added by default unless you add them using "app add".
+DISCLAIMER: Not all applications are suitable for labtest lock mode.  For example, VSCode
+            requires access to the terminal for compiling and debugging code.
+            Consult with tech when adding new applications in lock mode.
+In regular labtest mode, these other applications are added by default:
+org.gnome.Ptyxis
+eclipse
+org.gnome.Nautilus
+NOTE: If you add an app, but still want some of the defaults, you will have to re-add the defaults.
+NOTE:
+app default                                Delete custom app list
+app list                                   List custom app list
+app add <app>                              Add app to custom app list
+app delete <app>                           Delete app from custom app list
+app edit                                   Edit app list in text editor
+app help                                   Display this help text
+</code>
+===== EECSVM Help =====
+<code>
+Labtest (7777A) [labtest1]  > eecsvm help
+EECSVM Mode Help:
+The EECSVM service allows students to use virtual machines required by courses
+they are taking. The service is only available to students enrolled in courses
+requiring this service, and the respective faculty.
+By default, EECSVM service is NOT available in Labtest mode.  It can be enabled
+(or disabled) with the options below.  When enabled, users do not have access
+to VMs that they have created outside of Labtest mode - only the template VMs.
+eecsvm enable                               Enable EESCVM mode
+eecsvm disable                              Disable EECSVM mode
+eecsvm help                                 Display this help text
+For more information on EECSVM service, please refer to this page:
+https://wiki.eecs.yorku.ca/dept/tdb/services:eecsvm
+</code>
 ===== Labtest Lock =====
@@ Line 193: / Line 257: @@
 In labtest lock mode, the student is placed in a limited environment
 with no access to a terminal.  By default, the only application available
-is Firefox web browser.  Additional applications can be made available.
+is Firefox web browser.  Additional applications can be made available
+(see "apps help").
 lock enable                                 Enable lock mode
 lock disable                                Disable lock mode
-lock list                                   List apps in lock mode
-lock add <app> [<opts>] [<display-name>]    Add app to lock mode
-lock delete <app>                           Delete app from lock mode
-lock help                                   Display this help text
-NOTE: As there is no access to a terminal, apps must bring up a GUI.
-Example:
 Enable lock mode (by default includes Web browser access only):
@@ Line 210: / Line 267: @@
 > lock enable
-Want to make Eclipse available in lock mode?
+Disable lock mode:
-> lock add eclipse
+> lock disable
-Add Matlab to lock mode (requires the option -desktop):
-> lock add matlab -desktop
-DISCLAIMER: Not all applications are suitable for lock mode.  For example, VSCode
-            requires access to the terminal for compiling and debugging code.
 </code>
@@ Line 380: / Line 431: @@
 # labtest1-LAB1
 # version: labtest1-lab1
-/20/2023   09:54 5 labtest ea 01-78
+/20/2023   09:55 5 labtest ea 01-78
 /20/2023   11:45 5 default ea 01-78
 </code>
@@ Line 386: / Line 437: @@
 Description:
-  * On June 20, 2023 at 9:54 AM, machines ea01-ea78 in las1006 will display (to logged in users) a warning that the machines will reboot in 5 minutes into labtest mode.  The machines will remind students once per minute until the 5 minutes have elapsed.
+  * On June 20, 2023 at 9:55 AM, machines ea01-ea78 in las1006 will display (to logged in users) a warning that the machines will reboot in 5 minutes into labtest mode.  The machines will remind students once per minute until the 5 minutes have elapsed. (You could also use "4" instead of "5" in the third column to give 4 minutes of warnings, and a reboot at 9:59 so the machines are ready by 10.)
-  * The machines will reboot into labtest mode at 9:59 AM, so they should be ready by 10:00 AM.
+  * The machines will reboot into labtest mode at 9:55 AM, so they should be ready by 10:00 AM.
   * On June 20, 2023 at 11:45 AM, machines ea01-ea78 in las1006 will display (to logged in users) a warning that the machines will reboot back to Linux mode in 5 minutes.  The machines will remind students once per minute until the 5 minutes have elapsed.
-  * At 11:50 PM, machines will reboot from Labest mode back to Linux mode.
+  * At 11:50 PM, machines will reboot from Labtest mode back to Linux mode.
 **Please ensure that your labtest ends 10 minutes prior to the end of your lab booking time.**  For example, if your lab time is 10:00 AM - 11:30 AM, then the students should receive their 5 minute warning at 11:45 AM, then the machines will reboot at 11:50 AM.
@@ Line 398: / Line 449: @@
 # labtest1-LAB1
 # version: labtest1-lab1
-/20/2023   09:54 5 labtest ea 01-78
+/20/2023   09:55 5 labtest ea 01-78
 /20/2023   11:45 5 default ea 01-78
 </code>
@@ Line 407: / Line 458: @@
 # labtest1-LAB1 MAIN
 # version: labtest1-lab1
-/20/2023   09:54 5 labtest ea 01-70
+/20/2023   09:55 5 labtest ea 01-70
 /20/2023   11:45 5 default ea 01-70
 # labtest1-LAB1 ACCOMMODATION - 5 machines getting extra hour
 # version: labtest1-lab1
-/20/2023   09:54 5 labtest ea 71-75
+/20/2023   09:55 5 labtest ea 71-75
 /20/2023   12:45 5 default ea 71-75
 # labtest1-LAB1 ACCOMMODATION - 2 students getting extra 30 minutes
 # version: labtest1-lab1
-/20/2023   09:54 5 labtest ea 76-77
+/20/2023   09:55 5 labtest ea 76-77
 /20/2023   12:15 5 default ea 76-77
 # labtest1-LAB1 ACCOMMODATION - 1 student getting extra 20 minutes
 # version: labtest1-lab1
-/20/2023   09:54 5 labtest ea78
+/20/2023   09:55 5 labtest ea78
 /20/2023   12:05 5 default ea78
 </code>
@@ Line 945: / Line 996: @@
 Now if you test your labtest in ltcloud, the user will only be able to access the Firefox web browser.
-If you want additional software to be accessible in labtest, it must use a GUI.  You add to the lock file lines of the following format:
+If you want additional software to be accessible in labtest, create a file in the labtest folder called "apps" (eg. /eecs/dept/www/course/9999/labtest/default/apps).  The file contains a list of ".desktop" files available on the system for Applications that you wish to be included in the app dock at the bottom of the screen. A .desktop file is a plain text configuration file used in Linux and Unix-like operating systems to create application shortcuts, define program launchers, and integrate software into a desktop environment's application menu.
-  <app name>,<OPTIONAL app arguments>,<OPTIONAL app display name>
-For example, if you want Eclipse to be available in lock mode, you would add to the lock file:
-  eclipse
-By default, there are no optional arguments, and if no alternate display name is mentioned, then it will appear in the menu with the same name as the command name, but with the first letter capitalized ("Eclipse").
-If you want to add Matlab:
+These applications are ALWAYS included no matter what your settings: Firefox, Logout, and LTRestore
-  matlab,-desktop
+In labtest lock mode, no additional applications are added by default unless you add them to the app file.
-In order to run "Matlab", we have to pass "-desktop".  It would appear in the menu as "Matlab".
+**DISCLAIMER: Not all applications are suitable for labtest lock mode.  For example, VSCode requires access to the terminal for compiling and debugging code. Consult with tech when adding new applications in lock mode. **
-On the other hand, if you wanted to include Visual Studio Code, you would add:
+In regular labtest mode, these other applications are added by default:
-  code,,Visual Studio Code
+org.gnome.Ptyxis (this is the terminal)
+eclipse
+org.gnome.Nautilus (this is the file manager)
-Now, "Visual Studio Code" will be displayed in the menu, but it will execute the command "code".
+If you want to add an app, you need to find the desktop file for the app.  Desktop files are located in /eecs/local/share/applications/*.desktop.
-In labtest lock mode, the window environment is a little different in order to support the locked down nature of the environment.
+If you add an app, but still want some of the defaults to appear, you have to add the defaults back as well.  For example, if you want to add IntelliJ, but you want to continue with the existing defaults, then create the "app" file containing:
-When labtest mode is started, a web browser will appear with the labtest start page.  Additional software will be available by right clicking the desktop, or by clicking on the "Apps & Logout" menu in the bottom left corner of the desktop.
+idea <- that's intellij
+org.gnome.Ptyxis (this is the terminal)
+eclipse
+org.gnome.Nautilus (this is the file manager)
-Please ensure that you're careful when allowing access to software in lock mode.  Giving access to additional software may have unintended side effects.  For example, if you allow access to Eclipse, then students can compile and run code which can give access to system resources that would otherwise not be available.  Access to a terminal is still blocked.
+** Please ensure that you're careful when allowing access to software in lock mode.  Giving access to additional software may have unintended side effects.  For example, if you allow access to Eclipse, then students can compile and run code which can give access to system resources that would otherwise not be available.  Access to a terminal is still blocked. **
 ====== Accessing External Hosts In Labtest (optional) ======
@@ Line 1571: / Line 1619: @@
 Sometimes, during labtest mode, you may require a student to move from one machine to another machine.  This may be because the student is in the wrong area of the lab, or because there is some failure on the machine (eg. monitor).  Labtest home directories are stored on the local machine, and not a network drive.  Moving a student to another machine without some mechanism to copy student files from one machine to the other would mean starting with a brand new home directory, no files, and an unhappy student!
-When a student moves from one machine to the another, and logs in, the system will check if the student has files from another machine stored in the labtest save cache.  If they do, the student will see the following message: "Welcome!  It seems you have worked on this labtest on another machine.  You may ask one of the test supervisors for approval to transfer your work to this machine, or, hit Cancel to start again.".  At this point, if the student hits "Cancel", then they are logged in with a new environment without restoring their files.  If they want to restore their files from another machine, they need either **your** or your TAs approval!
+When a student moves from one machine to the another, files are not copied automatically.  Once the student logs in, they should click on the "LTRestore" icon which is located on the dock at the bottom of the screen.  The student will see the following message: "This app allows a labtest administrator to restore your work fro ma previous session. Do you need to restore work from a previous session?".  If they click "Yes", then either the faculty or the TA (who has been specified in the admin list for the labtest) must authenticate.
 To restore a students files from another machine, you will need to enter 3 pieces of information -- Labtest Admin (userid), Password, and Restore Machine.  Select the labtest admin from the dropdown list.  The labtest admins are specified by you when you request labtest mode.  The admins are also displayed in the pcmode schedule.  It's important that you check the list of admins before every labtest because neither the lab monitor nor tech staff will be able to restore a students files.   After selecting your name from the admin list, enter your system password.   Next, under "Restore Machine", a dropdown box lists all the machines where the student has been.  Select a machine from which you wish to restore the students files, and click "OK".