243
edits
Tonyhanson (talk | contribs) No edit summary |
Tonyhanson (talk | contribs) No edit summary |
||
Line 69: | Line 69: | ||
Note that many hosting services do not allow access to the shell by default. You may need to contact them and request permission. | Note that many hosting services do not allow access to the shell by default. You may need to contact them and request permission. | ||
Once you have access to the shell you can create files with valid commands in them. One common use is to create backup files.Here is a typical sample presented only to illustrate the basic concepts. | |||
<pre>MON=`date | cut -c5-7` | |||
DAY=`date | cut -c9-10` | |||
YR=`date | cut -c25-28` | |||
TIM=`date | cut -c12-19 | sed 's/:/_/g'` | |||
DAT_TIM=`echo $DAY"_"$MON"_"$YR"_"$TIM` | |||
cd /home8/dallasge/public_html | |||
FILENAME=$BUD"/"$DAT_TIM"_public_html_Production.tar.gz" | |||
tar --create --gzip --file=$FILENAME Production</pre> | |||
After creating and saving this file (say, for example, in a file named DailyBackups) you would tell the shell that it was an executable program my changing the file attributes using the chmod command: | |||
<pre>chmod +x DailyBackups</pre> | |||
You could then run the file by typing this at the shell prompt (from the same directory): | |||
<pre>DailyBackups</pre> | |||
This would tell the system to run your shell and create a backup file named 29_Jan_2011_01_30_02_public_html_Production.tar.gz | |||
== Text Editors == | == Text Editors == |
edits