Internals - crontab is now customized with MACHINENAME

docs/hpc/3stampede/admin.md

@@ -144,6 +144,6 @@ $ module help            # show help text for the module system itself
 
 It's safe to execute module commands in job scripts. In fact, this is a good way to write self-documenting, portable job scripts that produce reproducible results.  If you use `module save` to define a personal default module collection, it's rarely necessary to execute module commands in shell startup scripts, and it can be tricky to do so safely. If you do wish to put module commands in your startup scripts, see Stampede3's default startup scripts in `/usr/local/startup_scripts` for a safe way to do so.
 
-{% include 'include/crontabs.md' %}
+{% include 'include/stampede3-crontab.md' %}
 
 {% include 'include/tacctips.md' %}

docs/hpc/6lonestar/admin.md

@@ -187,7 +187,7 @@ See [Lmod's online documentation](http://lmod.readthedocs.org) for more extensiv
 
 It's safe to execute module commands in job scripts. In fact, this is a good way to write self-documenting, portable job scripts that produce reproducible results. If you use `module save` to define a personal default module collection, it's rarely necessary to execute module commands in shell startup scripts, and it can be tricky to do so safely. If you do wish to put module commands in your startup scripts, see Lonestar6's default startup scripts for a safe way to do so.
 
-{% include 'include/crontabs.md' %}
+{% include 'include/lonestar6-crontab.md' %}
 
 
 {% include 'include/tacctips.md' %}

docs/hpc/frontera.md

@@ -230,7 +230,7 @@ See [Lmod's online documentation](http://lmod.readthedocs.org) for more extensiv
 
 It's safe to execute module commands in job scripts. In fact, this is a good way to write self-documenting, portable job scripts that produce reproducible results. If you use `module save` to define a personal default module collection, it's rarely necessary to execute module commands in shell startup scripts, and it can be tricky to do so safely. If you do wish to put module commands in your startup scripts, see Frontera's default startup scripts for a safe way to do so.
 
-{% include 'include/crontabs.md' %}
+{% include 'include/frontera-crontab.md' %}
 
 {% include 'include/tacctips.md' %}
 

docs/hpc/frontera/admin.md

@@ -190,7 +190,7 @@ See [Lmod's online documentation](http://lmod.readthedocs.org) for more extensiv
 
 It's safe to execute module commands in job scripts. In fact, this is a good way to write self-documenting, portable job scripts that produce reproducible results. If you use `module save` to define a personal default module collection, it's rarely necessary to execute module commands in shell startup scripts, and it can be tricky to do so safely. If you do wish to put module commands in your startup scripts, see Frontera's default startup scripts for a safe way to do so.
 
-{% include 'include/crontabs.md' %}
+{% include 'include/frontera-crontab.md' %}
 
 {% include 'include/tacctips.md' %}
 

docs/hpc/lonestar6.md

@@ -442,7 +442,7 @@ See [Lmod's online documentation](http://lmod.readthedocs.org) for more extensiv
 
 It's safe to execute module commands in job scripts. In fact, this is a good way to write self-documenting, portable job scripts that produce reproducible results. If you use `module save` to define a personal default module collection, it's rarely necessary to execute module commands in shell startup scripts, and it can be tricky to do so safely. If you do wish to put module commands in your startup scripts, see Lonestar6's default startup scripts for a safe way to do so.
 
-{% include 'include/crontabs.md' %}
+{% include 'include/lonestar6-crontab.md' %}
 
 
 {% include 'include/tacctips.md' %}

docs/hpc/stampede3.md

@@ -301,7 +301,7 @@ $ module help            # show help text for the module system itself
 
 It's safe to execute module commands in job scripts. In fact, this is a good way to write self-documenting, portable job scripts that produce reproducible results.  If you use `module save` to define a personal default module collection, it's rarely necessary to execute module commands in shell startup scripts, and it can be tricky to do so safely. If you do wish to put module commands in your startup scripts, see Stampede3's default startup scripts in `/usr/local/startup_scripts` for a safe way to do so.
 
-{% include 'include/crontabs.md' %}
+{% include 'include/stampede3-crontab.md' %}
 
 {% include 'include/tacctips.md' %}
 ## Managing Your Files { #files }

docs/hpc/vista.md

@@ -27,7 +27,7 @@ Vista is funded by the National Science Foundation (NSF) via a supplement to the
 
 ## Account Administration
 
-{% include 'include/crontabs.md' %}
+{% include 'include/vista-crontab.md' %}
 
 {% include 'include/tacctips.md' %}
 

docs/hpc/vista/admin.md

@@ -1,6 +1,6 @@
 ## Account Administration
 
-{% include 'include/crontabs.md' %}
+{% include 'include/vista-crontab.md' %}
 
 {% include 'include/tacctips.md' %}
 

docs/include/configurestrings.sh

@@ -7,13 +7,16 @@ if [ "$1" = "frontera" ]
 then
 	echo "building includes for Frontera user guide"
 	machinename="Frontera"
+	lcmachinename="frontera"
 	helpoutputfile="frontera-help.md"
 	jobaccountingoutputfile="frontera-jobaccounting.md"
+	crontaboutputfile="frontera-crontab.md"
 	hwthreads="56 on CLX"
 	mkloutputfile="frontera-mkl.md"
 	helpmsg="Be sure to include \"$machinename\" in the Resource field."
 
 	sed	-e "s/MACHINENAME/$machinename/g" < jobaccountingsrc.md > $jobaccountingoutputfile
+	sed	-e "s/MACHINENAME/$lcmachinename/g" < crontabsrc.md > $crontaboutputfile
 
 	sed	-e "s/HWTHREADS/$hwthreads/g" < mklsrc.md > $mkloutputfile
 
@@ -25,12 +28,16 @@ elif [ "$1" = "vista" ]
 then
 	echo "building includes for Vista user guide"
 	machinename="Vista"
+	lcmachinename="vista"
 	helpoutputfile="vista-help.md"
 	jobaccountingoutputfile="vista-jobaccounting.md"
+	crontaboutputfile="vista-crontab.md"
 	helpmsg="Be sure to include \"$machinename\" in the Resource field."
 
 	sed	-e "s/MACHINENAME/$machinename/g" < jobaccountingsrc.md > $jobaccountingoutputfile
 
+	sed	-e "s/MACHINENAME/$lcmachinename/g" < crontabsrc.md > $crontaboutputfile
+
 	sed	-e "s/MACHINENAME/$machinename/g" \
 		-e "s/HELPMSG/$helpmsg/g" < helpsrc.md > $helpoutputfile
 
@@ -39,14 +46,18 @@ elif [ "$1" = "lonestar6" ]
 then
 	echo "building includes for Lonestar6 user guide"
 	machinename="Lonestar6"
+	lcmachinename="lonestar6"
 	helpoutputfile="lonestar6-help.md"
 	jobaccountingoutputfile="lonestar6-jobaccounting.md"
+	crontaboutputfile="lonestar6-crontab.md"
 	hwthreads="128 on AMD Milan"
 	mkloutputfile="lonestar6-mkl.md"
 	helpmsg="Be sure to include \"$machinename\" in the Resource field."
 
 	sed	-e "s/MACHINENAME/$machinename/g" < jobaccountingsrc.md > $jobaccountingoutputfile
 
+	sed	-e "s/MACHINENAME/$lcmachinename/g" < crontabsrc.md > $crontaboutputfile
+
 	sed	-e "s/HWTHREADS/$hwthreads/g" < mklsrc.md > $mkloutputfile
 
 	sed	-e "s/MACHINENAME/$machinename/g" \
@@ -57,12 +68,16 @@ elif [ "$1" = "stampede3" ]
 then
 	echo "building includes for Stampede3 user guide"
 	machinename="Stampede3"
+	lcmachinename="stampede3"
 	helpoutputfile="stampede3-help.md"
 	jobaccountingoutputfile="stampede3-jobaccounting.md"
+	crontaboutputfile="stampede3-crontab.md"
 	helpmsg="Be sure to include \"$machinename\" in the Resource field."
 
 	sed	-e "s/MACHINENAME/$machinename/g" < jobaccountingsrc.md > $jobaccountingoutputfile
 
+	sed	-e "s/MACHINENAME/$lcmachinename/g" < crontabsrc.md > $crontaboutputfile
+
 	sed	-e "s/MACHINENAME/$machinename/g" \
 		-e "s/HELPMSG/$helpmsg/g" < helpsrc.md > $helpoutputfile
 

docs/include/crontabsrc.md

@@ -0,0 +1,24 @@
+### Crontabs
+
+TACC allows cronjobs but be aware that crontab files are unique to the login node where they were created and are not shared across the login nodes.  Crontab files are not allowed on the compute nodes.  
+
+!!! note
+	All TACC HPC systems host multiple login nodes.  When you login, your connection is routed to the next available login node via round-robin DNS.   This practice balances the user load across the system.  
+
+When creating a crontab file, use the `hostname` command to determine your exact location, and make note of it:
+
+```cmd-line
+$ hostname
+login2.MACHINENAME.tacc.utexas.edu
+```
+
+Similarly you can always connect to that login node by specifying its full domain name:
+
+```cmd-line
+localhost$ ssh login2.MACHINENAME.tacc.utexas.edu
+```
+
+!!! important
+	As with any computation, ensure that cronjobs are run only on the compute nodes
+
+

docs/include/crontabs.md → docs/include/frontera-crontab.md

@@ -9,12 +9,13 @@ When creating a crontab file, use the `hostname` command to determine your exact
 
 ```cmd-line
 $ hostname
-login3.stampede3.tacc.utexas.edu
+login2.frontera.tacc.utexas.edu
 ```
+
 Similarly you can always connect to that login node by specifying its full domain name:
 
 ```cmd-line
-localhost$ ssh login3.stampede3.tacc.utexas.edu
+localhost$ ssh login2.frontera.tacc.utexas.edu
 ```
 
 !!! important

docs/include/lonestar6-crontab.md

@@ -0,0 +1,24 @@
+### Crontabs
+
+TACC allows cronjobs but be aware that crontab files are unique to the login node where they were created and are not shared across the login nodes.  Crontab files are not allowed on the compute nodes.  
+
+!!! note
+	All TACC HPC systems host multiple login nodes.  When you login, your connection is routed to the next available login node via round-robin DNS.   This practice balances the user load across the system.  
+
+When creating a crontab file, use the `hostname` command to determine your exact location, and make note of it:
+
+```cmd-line
+$ hostname
+login2.lonestar6.tacc.utexas.edu
+```
+
+Similarly you can always connect to that login node by specifying its full domain name:
+
+```cmd-line
+localhost$ ssh login2.lonestar6.tacc.utexas.edu
+```
+
+!!! important
+	As with any computation, ensure that cronjobs are run only on the compute nodes
+
+

docs/include/stampede3-crontab.md

@@ -0,0 +1,24 @@
+### Crontabs
+
+TACC allows cronjobs but be aware that crontab files are unique to the login node where they were created and are not shared across the login nodes.  Crontab files are not allowed on the compute nodes.  
+
+!!! note
+	All TACC HPC systems host multiple login nodes.  When you login, your connection is routed to the next available login node via round-robin DNS.   This practice balances the user load across the system.  
+
+When creating a crontab file, use the `hostname` command to determine your exact location, and make note of it:
+
+```cmd-line
+$ hostname
+login2.stampede3.tacc.utexas.edu
+```
+
+Similarly you can always connect to that login node by specifying its full domain name:
+
+```cmd-line
+localhost$ ssh login2.stampede3.tacc.utexas.edu
+```
+
+!!! important
+	As with any computation, ensure that cronjobs are run only on the compute nodes
+
+

docs/include/vista-crontab.md

@@ -0,0 +1,24 @@
+### Crontabs
+
+TACC allows cronjobs but be aware that crontab files are unique to the login node where they were created and are not shared across the login nodes.  Crontab files are not allowed on the compute nodes.  
+
+!!! note
+	All TACC HPC systems host multiple login nodes.  When you login, your connection is routed to the next available login node via round-robin DNS.   This practice balances the user load across the system.  
+
+When creating a crontab file, use the `hostname` command to determine your exact location, and make note of it:
+
+```cmd-line
+$ hostname
+login2.vista.tacc.utexas.edu
+```
+
+Similarly you can always connect to that login node by specifying its full domain name:
+
+```cmd-line
+localhost$ ssh login2.vista.tacc.utexas.edu
+```
+
+!!! important
+	As with any computation, ensure that cronjobs are run only on the compute nodes
+
+