Groovix Net Control - Revision history

imported>GroovixAdmin at 16:19, 31 March 2020

2020-03-31T16:19:50Z

← Older revision		Revision as of 16:19, 31 March 2020
Line 3:		Line 3:
	The Groovix system provides all networked workstations with unified profiles and software updates as part of the Groovix update process. This process is done through a system called Groovix Net Control or GNC. It queries updates, fixes and system changes from the [[Groovix Server]] and runs them automatically. If the system has not applied these updates, they are downloaded and installed automatically.		The Groovix system provides all networked workstations with unified profiles and software updates as part of the Groovix update process. This process is done through a system called Groovix Net Control or GNC. It queries updates, fixes and system changes from the [[Groovix Server]] and runs them automatically. If the system has not applied these updates, they are downloaded and installed automatically.

	Normally, this process is performed on boot up, or can be customized to a specific update schedule; however, this process can be run manually at any time by typing <font class="code">groovix-net-control</font> in an [[xterm]] window. Every time Groovix Net Control is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at <font class="code">/var/log/groovix/net-control/gnc.log</font>.		Normally, this process is performed on boot up, or can be customized to a specific update schedule; however, this process can be run manually at any time by typing <font class="code">groovix-net-control</font> in an [[xterm]] window. Every time Groovix Net Control is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at <font class="code">/var/log/groovix/net-control/gnc.log </font> .

	== GNC Scripts ==		== GNC Scripts ==

imported>GroovixAdmin at 16:19, 31 March 2020

2020-03-31T16:19:33Z

← Older revision		Revision as of 16:19, 31 March 2020
Line 3:		Line 3:
	The Groovix system provides all networked workstations with unified profiles and software updates as part of the Groovix update process. This process is done through a system called Groovix Net Control or GNC. It queries updates, fixes and system changes from the [[Groovix Server]] and runs them automatically. If the system has not applied these updates, they are downloaded and installed automatically.		The Groovix system provides all networked workstations with unified profiles and software updates as part of the Groovix update process. This process is done through a system called Groovix Net Control or GNC. It queries updates, fixes and system changes from the [[Groovix Server]] and runs them automatically. If the system has not applied these updates, they are downloaded and installed automatically.

	Normally, this process is performed on boot up, or can be customized to a specific update schedule; however, this process can be run manually at any time by typing <font class="code">groovix-net-control</font> in an [[xterm]] window. Every time Groovix Net Control is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at <font class="code">/var/log/groovix/net-control/gnc.log</font>~~, note that this only contains information from the last time GNC was run~~.		Normally, this process is performed on boot up, or can be customized to a specific update schedule; however, this process can be run manually at any time by typing <font class="code">groovix-net-control</font> in an [[xterm]] window. Every time Groovix Net Control is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at <font class="code">/var/log/groovix/net-control/gnc.log</font>.


	== GNC Scripts ==		== GNC Scripts ==

imported>GroovixAdmin at 16:18, 31 March 2020

2020-03-31T16:18:42Z

← Older revision		Revision as of 16:18, 31 March 2020
Line 4:		Line 4:

	Normally, this process is performed on boot up, or can be customized to a specific update schedule; however, this process can be run manually at any time by typing <font class="code">groovix-net-control</font> in an [[xterm]] window. Every time Groovix Net Control is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at <font class="code">/var/log/groovix/net-control/gnc.log</font>, note that this only contains information from the last time GNC was run.		Normally, this process is performed on boot up, or can be customized to a specific update schedule; however, this process can be run manually at any time by typing <font class="code">groovix-net-control</font> in an [[xterm]] window. Every time Groovix Net Control is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at <font class="code">/var/log/groovix/net-control/gnc.log</font>, note that this only contains information from the last time GNC was run.


	== Setting up Groovix Server for GNC ==
	Coming Soon

imported>GroovixAdmin at 21:22, 2 April 2017

2017-04-02T21:22:19Z

← Older revision		Revision as of 21:22, 2 April 2017
Line 1:		Line 1:
	__TOC__		__TOC__

	The Groovix system provides all networked workstations with unified profiles and software updates as part of the Groovix update process. This process is done through a system called Groovix ~~NetCustomization~~ or GNC. It queries updates, fixes and system changes from the [[Groovix Server]] and runs them automatically. If the system has not applied these updates, they are downloaded and installed automatically.		The Groovix system provides all networked workstations with unified profiles and software updates as part of the Groovix update process. This process is done through a system called Groovix Net Control or GNC. It queries updates, fixes and system changes from the [[Groovix Server]] and runs them automatically. If the system has not applied these updates, they are downloaded and installed automatically.

	Normally, this process is performed on boot up, or can be customized to a specific update schedule; however, this process can be run manually at any time by typing <font class="code">~~/etc/init.d/~~groovix-~~netcustomization start~~</font> in an [[xterm]] window. Every time Groovix ~~NetCustomization~~ is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at <font class="code">/var/log/groovix/~~netcustomization~~.log</font>, note that this only contains information from the last time GNC was run.		Normally, this process is performed on boot up, or can be customized to a specific update schedule; however, this process can be run manually at any time by typing <font class="code">groovix-net-control</font> in an [[xterm]] window. Every time Groovix Net Control is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at <font class="code">/var/log/groovix/net-control/gnc.log</font>, note that this only contains information from the last time GNC was run.

imported>GroovixAdmin: GroovixAdmin moved page Groovix NetCustomization to Groovix Net Control

2017-04-02T21:20:55Z

GroovixAdmin moved page Groovix NetCustomization to Groovix Net Control

← Older revision	Revision as of 21:20, 2 April 2017
(No difference)

imported>GroovixAdmin: /* GNC Script Commands */

2016-08-12T22:34:59Z

GNC Script Commands

← Older revision		Revision as of 22:34, 12 August 2016
Line 61:		Line 61:
	* --background : run this update in the background, like putting an & after a command in a shell, not recommended		* --background : run this update in the background, like putting an & after a command in a shell, not recommended

	=== GNC Script Commands ===		=== GNC Script Helper Commands ===
	* gncget [filename] - gets file and places it in that same location ,		* gncget [filename] - gets file and places it in that same location ,
	** use --mod 644 to set the file permissions or it will by 700		** use --mod 644 to set the file permissions or it will by 700

imported>GroovixAdmin: /* GNC Control Parameters */

2016-08-12T22:34:38Z

GNC Control Parameters

imported>GroovixAdmin: /* GNC Script Parameters */

2016-08-12T22:33:47Z

GNC Script Parameters

@@ Line 35: / Line 35: @@
-=== GNC Script Parameters ===
+=== GNC Control Parameters ===
-* --abort - exits the script if an error occurs so it can be run again. Avoid the abort flag for conditional arguments (like If statements) or use <font class-"code">set +e</font> before the conditional and <font class-"code">set -e</font> after the conditional in your script.
+--abort : exits the script if an error occurs so it can be run again.  Avoid the abort flag for scripts with conditional arguments (like If statements) or use set +e before the conditional and set -e after the conditional in your script.
 === GNC Script Commands ===

imported>GroovixAdmin: /* GNC Scripts */

2016-08-12T22:04:55Z

GNC Scripts

← Older revision		Revision as of 22:04, 12 August 2016
Line 15:		Line 15:
	The <font class="code">/var/www/groovix/gnc/updates/[customer]</font> directory contains separate directories for the different types, sites, and labels for your deployment. GNC updates that only apply to a specific workstation type (ex. web, kiosk type) should be placed in the directory for that type (ex. /var/lib/groovix/updates/web/). Updates placed in the <font class="code">/var/www/groovix/gnc/updates/default</font> directory are applied to all workstations.		The <font class="code">/var/www/groovix/gnc/updates/[customer]</font> directory contains separate directories for the different types, sites, and labels for your deployment. GNC updates that only apply to a specific workstation type (ex. web, kiosk type) should be placed in the directory for that type (ex. /var/lib/groovix/updates/web/). Updates placed in the <font class="code">/var/www/groovix/gnc/updates/default</font> directory are applied to all workstations.

	Each workstation downloads and executes the script individually after downloading it from Open Sense servers or your local [[Groovix Server]]. GNC updates that have been downloaded and executed can be found locally on each workstation in the <font class="code">/var/lib/groovix/updates/master.bash</font> file. To check that a specific GNC script was successful, a file named <font class="code">complete</font> can be found on the local machine under the directory name of that update <font class="code">/var/lib/groovix/updates/[updatename]/</font>.		Each workstation downloads and executes the script individually after downloading it from Open Sense servers or your local [[Groovix Server]]. GNC updates that have been downloaded and executed can be found locally on each workstation in the <font class="code">/var/lib/groovix/updates/master.bash</font> file.


	=== Script Structure ===		=== Script Structure ===
			To have predictable results with the order in which GNC scripts are run, the GNC_ORDER= variable in the gnc file is used. The order can be a decimal and typically it is a representation of the date and time that you created or updated the gnc, ex. 20160215.162800 for February 15th at 4:28 pm.
	To have predictable results with how GNC scripts are run, each GNC directory name should follow a formula of a four digit number and a short description of the update, with dashes ( - ) used instead of spaces and a -1 at the end. If an update changes its function over time or is re-purposed, change the -1 to a -2, -3, etc. to the end of the new update (ex. 0125-gdm-fix-2); this ensures that this update is applied after the older version and that workstations that already have this update, run it again with the latest change(s).

	When a Groovix workstation downloads multiple updates, it runs them in sequential order. 0-1000 should be reserved for GNC updates that are required to be run before other updates, 2000's should be used for most typical updates that require no specific order of importance, and 9000's should be reserved for GNC updates that need to be run last, or after other updates.		When a Groovix workstation downloads multiple updates, it runs them in sequential order. 0-1000 should be reserved for GNC updates that are required to be run before other updates, 2000's should be used for most typical updates that require no specific order of importance, and 9000's should be reserved for GNC updates that need to be run last, or after other updates.

			When you create a new gnc with the gnc-new command the GNC_ORDER= will automatically be set. When you edit a gnc and want the update to be re-applied to machines that have already run it succesfully, run gnc-bump [updatename] to update the GNC_ORDER= variable in the gnc.
	If timing is not critical to run an update, begin the update name with the date the update is created starting with the year (ex. 20120101-floppy-fix). Only use the 1000's or 9000's if your GNC update is required to be run before or after all other updates.


	=== Script Rules & Formatting ===		=== Script Rules & Formatting ===
	* Each update must have a gnc file in the root of the update directory		* Each update must have a gnc file in the root of the update directory
	* Update directories are named ~~with~~ a ~~number~~, ~~followed~~ by ~~the~~ ~~description~~		* Update directories are typically named for what they do and can contain letters, numbers, dashes, and underscores
	* Update directories named with 0000-1000 are run first		* Update directories named with 0000-1000 are run first
	* Update directories named by date (20110228) run after initial updates		* Update directories named by date (20110228) run after initial updates
	* Update directories named 9000+ are run after all other updates		* Update directories named 9000+ are run after all other updates
	* If files are included in your update other than gnc, create the directory structure those files will reside in		* If files are included in your update other than gnc, create the directory structure those files will reside in, i.e. mkdir -p [updatename]/etc/cups/printers.conf
	* The first line of the gnc batch script contains the parameters that dictate how the update will be ran		* The first line of the gnc batch script contains the parameters that dictate how the update will be ran


	=== GNC Script Parameters ===		=== GNC Script Parameters ===
	* abort - exits the script if an error occurs so it can be run again. Avoid the abort flag for conditional arguments (like If statements) or use <font class-"code">set +e</font> before the conditional and <font class-"code">set -e</font> after the conditional in your script.		* --abort - exits the script if an error occurs so it can be run again. Avoid the abort flag for conditional arguments (like If statements) or use <font class-"code">set +e</font> before the conditional and <font class-"code">set -e</font> after the conditional in your script.
	* attemptonce - as soon as it attempts to run the update, it will never run it again.		* attemptonce - as soon as it attempts to run the update, it will never run it again.
	* background - no longer in use.		* background - no longer in use.
Line 51:		Line 50:

	=== GNC Script Commands ===		=== GNC Script Commands ===
	* gncget [filename] - gets file and places it in that same location		* gncget [filename] - gets file and places it in that same location ,
			** use --mod 644 to set the file permissions or it will by 700
⚫	* apt-get~~-dontask~~ install - unattended package install with all defaults
			** use --gunzip for big files, store it as .gz on the server but refer to it with the .gz in the gncget command, it will be automatically unzipped
⚫	* apt-get~~-dontask~~ remove - unattended package uninstall
			** use --tgz to get an entire directory at a time, use [dirname].tgz on the server and give the full path to the directory in the gncget command
⚫	* bashconfset~~.pl~~
		⚫	* groovix-auto-apt-get install - unattended package install with all defaults
⚫	* pyconfset~~.pl~~
		⚫	* groovix-auto-apt-get remove - unattended package uninstall
	* --mod 644 - allows file to be downloaded from server
		⚫	* bashconfset
	* --gunzip - will automatically look for .gz extension, download, unzip, and place the files
		⚫	* pyconfset
	* --tgz - will automatically tar and gzip

	== GNC Script Examples ==		== GNC Script Examples ==

imported>Chris at 03:53, 25 April 2012

2012-04-25T03:53:11Z

← Older revision		Revision as of 03:53, 25 April 2012
Line 3:		Line 3:
	The Groovix system provides all networked workstations with unified profiles and software updates as part of the Groovix update process. This process is done through a system called Groovix NetCustomization or GNC. It queries updates, fixes and system changes from the [[Groovix Server]] and runs them automatically. If the system has not applied these updates, they are downloaded and installed automatically.		The Groovix system provides all networked workstations with unified profiles and software updates as part of the Groovix update process. This process is done through a system called Groovix NetCustomization or GNC. It queries updates, fixes and system changes from the [[Groovix Server]] and runs them automatically. If the system has not applied these updates, they are downloaded and installed automatically.

	Normally, this process is performed on boot up, or can be customized to a specific update schedule; however, this process can be run manually at any time by typing <font class="code">/etc/init.d/groovix-netcustomization start</font> in an [[xterm]] window. Every time Groovix NetCustomization is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at <font class="code">/var/log/groovix/netcustomization.log</font>.		Normally, this process is performed on boot up, or can be customized to a specific update schedule; however, this process can be run manually at any time by typing <font class="code">/etc/init.d/groovix-netcustomization start</font> in an [[xterm]] window. Every time Groovix NetCustomization is run, the results of that process are dumped into a log file that can be accessed for reference or troubleshooting located at <font class="code">/var/log/groovix/netcustomization.log</font>, note that this only contains information from the last time GNC was run.


Line 12:		Line 12:
	== GNC Scripts ==		== GNC Scripts ==
	GNC updates are contained in their own directory in <font class="code">/var/www/groovix/gnc/updates/[customer]</font> where [customer] is the name of your Groovix site (Groovix site information can found in the <font class="code">/etc/groovix/version</font> file). Each GNC update has a file at the root of the directory called gnc; the gnc file is written in bash script as a series of commands listed in the order they should be run. Groovix provides parameters and commands that customize how and when GNC updates are run and which workstations will run them, these are described in more detail below.		GNC updates are contained in their own directory in <font class="code">/var/www/groovix/gnc/updates/[customer]</font> where [customer] is the name of your Groovix site (Groovix site information can found in the <font class="code">/etc/groovix/version</font> file). Each GNC update has a file at the root of the directory called gnc; the gnc file is written in bash script as a series of commands listed in the order they should be run. Groovix provides parameters and commands that customize how and when GNC updates are run and which workstations will run them, these are described in more detail below.

⚫	Each workstation downloads and executes the script individually after downloading it from Open Sense servers or your local [[Groovix Server]]. GNC updates that have been downloaded and executed can be found locally on each workstation in the <font class="code">/var/lib/groovix/updates/master.bash</font> file. To check that a specific GNC script was successful, a file named <font class="code">complete</font> can be found on the local machine under the directory name of that update <font class="code">/var/lib/groovix/updates/[updatename]/</font>.

	The <font class="code">/var/www/groovix/gnc/updates/[customer]</font> directory contains separate directories for the different types, sites, and labels for your deployment. GNC updates that only apply to a specific workstation type (ex. web, kiosk type) should be placed in the directory for that type (ex. /var/lib/groovix/updates/web/). Updates placed in the <font class="code">/var/www/groovix/gnc/updates/default</font> directory are applied to all workstations.		The <font class="code">/var/www/groovix/gnc/updates/[customer]</font> directory contains separate directories for the different types, sites, and labels for your deployment. GNC updates that only apply to a specific workstation type (ex. web, kiosk type) should be placed in the directory for that type (ex. /var/lib/groovix/updates/web/). Updates placed in the <font class="code">/var/www/groovix/gnc/updates/default</font> directory are applied to all workstations.

		⚫	Each workstation downloads and executes the script individually after downloading it from Open Sense servers or your local [[Groovix Server]]. GNC updates that have been downloaded and executed can be found locally on each workstation in the <font class="code">/var/lib/groovix/updates/master.bash</font> file. To check that a specific GNC script was successful, a file named <font class="code">complete</font> can be found on the local machine under the directory name of that update <font class="code">/var/lib/groovix/updates/[updatename]/</font>.


	=== Script Structure ===		=== Script Structure ===
	To have predictable results with how GNC scripts are run, each GNC directory name should follow a formula of a four digit number and a short description of the update. A ~~dash~~ ( - ) ~~should be~~ used instead of ~~any~~ spaces and ~~your~~ ~~script~~ ~~directory~~ ~~should~~ end ~~with~~ a ~~number~~ ~~based~~ on ~~how~~ ~~many~~ of ~~that~~ ~~type~~ ~~already exist; if none exist~~, ~~use~~ the ~~number 1 (ex. 20120101-homepage~~-1). As ~~your~~ ~~preferences~~ ~~and~~ ~~hardware~~ ~~change~~ ~~over time, you will~~ end ~~up with multiple scripts~~ of the ~~same~~ ~~type~~ ~~which~~ ~~could~~ ~~conflict~~ ~~with~~ ~~one another;~~ this ~~last~~ ~~number~~ ~~makes~~ ~~sure~~ the ~~most~~ ~~recent~~ ~~script~~ is ~~run~~ ~~last,~~ ~~(ex.~~ ~~0600-desktop-fix-1~~ ~~will~~ run ~~prior~~ to ~~0600-desktop-fix-2~~).		To have predictable results with how GNC scripts are run, each GNC directory name should follow a formula of a four digit number and a short description of the update, with dashes ( - ) used instead of spaces and a -1 at the end. If an update changes its function over time or is re-purposed, change the -1 to a -2, -3, etc. to the end of the new update (ex. 0125-gdm-fix-2); this ensures that this update is applied after the older version and that workstations that already have this update, run it again with the latest change(s).

	When a Groovix workstation downloads multiple updates, it runs them in sequential order. 0-1000 is reserved for GNC updates that ~~need~~ to be run ~~first~~, 2000's ~~are~~ ~~run~~ ~~next~~ ~~followed~~ by ~~9000 for GNC~~ updates that ~~need~~ to be ~~run~~ ~~last.~~ ~~If it is not critical to run an update~~, ~~begin~~ ~~the update name with the date the update is created starting with the year (ex. 20110101-floppy-fix). Only use the 1000~~'s or ~~9000's~~ if ~~your~~ GNC ~~update~~ is ~~required~~ to be run ~~before~~ or after ~~all~~ other updates. If an update changes its function over time or is repurposed, add a -1, -2, etc. to the end of the new update name (ex. 0125-gdm-fix-1); this ensures that this update is applied after the older version and that workstations that already have this update, run it again with the latest change(s).		When a Groovix workstation downloads multiple updates, it runs them in sequential order. 0-1000 should be reserved for GNC updates that are required to be run before other updates, 2000's should be used for most typical updates that require no specific order of importance, and 9000's should be reserved for GNC updates that need to be run last, or after other updates.

			If timing is not critical to run an update, begin the update name with the date the update is created starting with the year (ex. 20120101-floppy-fix). Only use the 1000's or 9000's if your GNC update is required to be run before or after all other updates.
	When you are ready to make your own GNC update, run the <font class="code">cp -rp var/www/groovix/gnc/doc/template/ [updatename]</font> command to create a copy of the template where [updatename] is the name of your update; make sure to name the update according to the rules mentioned above for best results.

← Older revision		Revision as of 22:34, 12 August 2016
Line 36:		Line 36:

	=== GNC Control Parameters ===		=== GNC Control Parameters ===
	--run (always\|once\|disabled) : always means run this each time GNC runs, once means don't run it after it has run succesfully, disabled means never run it		* --run (always\|once\|disabled) : always means run this each time GNC runs, once means don't run it after it has run succesfully, disabled means never run it
	--abort : exits the script if an error occurs so it can be run again. Avoid the abort flag for scripts with conditional arguments (like If statements) or use set +e before the conditional and set -e after the conditional in your script.		* --abort : exits the script if an error occurs so it can be run again. Avoid the abort flag for scripts with conditional arguments (like If statements) or use set +e before the conditional and set -e after the conditional in your script.
			*

	NOTE: all if and not statements are ANDed together - every single condition must be true for the update to run		* NOTE: all if and not statements are ANDed together - every single condition must be true for the update to run
	--if-mode (build\|install\|live\|normal) : only run this update if we are running in the specified mode		* --if-mode (build\|install\|live\|normal) : only run this update if we are running in the specified mode
	--not-mode (build\|install\|live\|normal) : do not run this update if we are running in the specified mode		* --not-mode (build\|install\|live\|normal) : do not run this update if we are running in the specified mode
	--if-group (site\|type\|label\|id) : only run this update if the machines site or type or label or id matched the specified group. all of those categories share a single namespace		* --if-group (site\|type\|label\|id) : only run this update if the machines site or type or label or id matched the specified group. all of those categories share a single namespace
	--not-group : do not run this update if the machines site or type or label or id matched the specified group. all of those categories share a single namespace		* --not-group : do not run this update if the machines site or type or label or id matched the specified group. all of those categories share a single namespace
	--if-from (startup\|shutdown\|ssh\|shell\|cmon) : run this update if gnc was started from the specified process		* --if-from (startup\|shutdown\|ssh\|shell\|cmon) : run this update if gnc was started from the specified process
	--not-from : do not run this update if gnc was started from the specified process		* --not-from : do not run this update if gnc was started from the specified process
			*
	--before [YYYYMMDDHHMM] : only run this gnc if the current time is before the specified datetime		* --before [YYYYMMDDHHMM] : only run this gnc if the current time is before the specified datetime
	--after [YYYYMMDDHHMM] : only run this gnc if the current time is after the specified datetime		* --after [YYYYMMDDHHMM] : only run this gnc if the current time is after the specified datetime
			*

	ADVANCED USAGE:		* ADVANCED USAGE:
	--depends [some-other-group/some-other-update] : this update should only be run if the specified update has successfully run		* --depends [some-other-group/some-other-update] : this update should only be run if the specified update has successfully run
	--overrides [some-other-group/some-other-update] : this update should be run again anytime the specified update is run		* --overrides [some-other-group/some-other-update] : this update should be run again anytime the specified update is run
	--cache : download and store this script on the hard drive so that even if it is not applicable to run now it can be run later even if there is no network connection		* --cache : download and store this script on the hard drive so that even if it is not applicable to run now it can be run later even if there is no network connection
	--rerun : run the entire GNC process again after processing this GNC, useful for gncs that change GNC parameters		* --rerun : run the entire GNC process again after processing this GNC, useful for gncs that change GNC parameters
	--continue : skip the rest of the gncs that were set to run in this iteration		* --continue : skip the rest of the gncs that were set to run in this iteration
	--break : stop running gnc after this update		* --break : stop running gnc after this update
	--reboot : reboot the computer after completing the entire GNC process, if you want an immediate reboot after this particular update then use the --break parameter as well		* --reboot : reboot the computer after completing the entire GNC process, if you want an immediate reboot after this particular update then use the --break parameter as well
	--fail-override ( warning\|disabled\|skip\|success\|complete) : no matter what the script returns, process the outcome as specified		* --fail-override ( warning\|disabled\|skip\|success\|complete) : no matter what the script returns, process the outcome as specified
	--background : run this update in the background, like putting an & after a command in a shell, not recommended		* --background : run this update in the background, like putting an & after a command in a shell, not recommended

	=== GNC Script Commands ===		=== GNC Script Commands ===