Zuletzt angesehen:
Seite anzeigen
Ältere Versionen

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung		Vorhergehende Überarbeitung
shell [2008/04/22 14:38] – shell bourne syntax IF vergleiche geraldshell [2024/02/29 13:36] (aktuell) – Externe Bearbeitung 127.0.0.1
Zeile 1: Zeile 1:
-A quick guide to writing scripts using the bash shell: 
-http://pegasus.rutgers.edu/~elflord/unix/bash-tute.html 
-Command Substitution: 
-http://www.injunea.demon.co.uk/pages/page206.htm 
-The Linux Terminal - a Beginners' Bash: 
-http://linux.org.mt/article/terminal 
  
-bash shell script: +{{tag>shell bash bourne .sh shellscript}}
-wichtug, dass am Anfang: +
-#!/bin/bash +
-Das ist wichtig, weil der User, sollte er eine andere Shell als Bash gew�lt haben, eine ander Syntax vorherrschen kann. +
-Variablen: +
-x="hallo" # wichtig: KEINE Leerzeichen bei dem '=' +
-$1, $2 etc. 1., 2., etc Parameter beim Aufruf +
-Um Variablen zu unterscheiden (z.B. /hallo/wer$binich/denn ist falsch, weil Interpreter nicht +
-weiss, wo Variable endet). Richtig: /hallo/wer${bin}ich/denn +
-Quoting: +
-bei echo '$x' kommt raus: $x +
-bei echo "$x" kommt raus: hallo +
-" interpretiert Variablen, +
-' tut das nicht! (sondern 'w�tlich') +
-parameter /variables substitution: +
-http://www.unet.univie.ac.at/aix/aixuser/usrosdev/parameter_subst.htm#AC8A8CF676shar+
  
-#!/bin/bash +siehe auch: [[bash]]
-X="" +
-if [ -n "$X" ]; then    # -n tests to see if the argument is non empty +
-        echo "the variable X is not the empty string" +
-else +
- echo "empty!" +
-fi+
  
-http://pegasus.rutgers.edu/~elflord/unix/bash-tute.html: +====== Bash Shell / Bourne Shell ======
-A brief summary of test operators+
  
- Here's a quick list of test operators. It's by no means comprehensive, but its likely to be all you'll need to remember (if you need anything else, you can always check the bash manpage ... ) +[[shell:if|IF-Operator]]
  
-operator +[[shell:in-out|Ein- und Ausgaben umleiten]]
-produces true if...  +
-number of operands+
  
--n +[[shell:shortcuts|Tastaturabkürzungen]]
-operand non zero length +
-1+
  
--z +[[shell:input Password|Passworteingabe über die Shell]]
-operand has zero length +
-1+
  
--d +[[shell:find|Text in einer Datei suchen]]
-there exists a directory whose name is operand +
-1+
  
--f +[[shell:email|eMail per Shellscript verschicken]]
-there exists a file whose name is operand +
-1+
  
--eq 
-the operands are integers and they are equal 
-2 
  
--neq +[[shell:explode|String nach bestimmten Zeichen splitten/cutten /wie explode in PHP)]]
-the opposite of -eq +
-2+
  
-= +[[http://tldp.org/LDP/abs/html/complexfunct.html|Complex Functions and Function Complexities]]
-the operands are equal (as strings) +
-2+
  
-!= +A quick guide to writing scripts using the bash shell: 
-opposite of =  +[[http://pegasus.rutgers.edu/~elflord/unix/bash-tute.html]]
-2+
  
--lt +Command Substitution: 
-operand1 is strictly less than operand2 (both operands should be integers) +[[http://www.injunea.demon.co.uk/pages/page206.htm]]
-2+
  
--gt +The Linux Terminal - a Beginners' Bash: 
-operand1 is strictly greater than operand2 (both operands should be integers) +[[http://linux.org.mt/article/terminal]]
-2+
  
--ge +Bash Shell Programming in Linux: 
-operand1 is greater than or equal to operand2 (both operands should be integers) +[[http://www.arachnoid.com/linux/shell_programming.html]]
-2+
  
--le +=== bash shell script: ===
-operand1 is less than or equal to operand2 (both operands should be integers) +
-2+
  
-Expressions may be unary or binary. Unary expressions are often used to examine the status of a file. There are string operators and numeric comparison operators as well. If the file argument to one of the primaries is of the form `/dev/fd/N', then file descriptor N is checked. If the file argument to one of the primaries is one of `/dev/stdin', `/dev/stdout', or `/dev/stderr', file descriptor 0, 1, or 2, respectively, is checked.  + 
--a file  +wichtig, dass am Anfang: 
-True if file exists.  +<code> 
--b file  +#!/bin/bash 
-True if file exists and is a block special file.  +</code> 
--c file  +Das ist wichtig, weil der User, sollte er eine andere Shell als Bash gewält haben, eine andere Syntax vorherrschen kann. 
-True if file exists and is a character special file.  +Variablen: 
--d file  +<code> 
-True if file exists and is a directory.  +x="hallo" # wichtig: KEINE Leerzeichen bei dem '=' 
--e file  +</code> 
-True if file exists.  + 
--f file  +$1, $2 etc. 1., 2., etc Parameter beim Aufruf 
-True if file exists and is a regular file.  +Um Variablen zu unterscheiden (z.B. /hallo/wer$binich/denn ist falsch, weil Interpreter nicht 
--g file  +weiss, wo Variable endet). Richtig: /hallo/wer${bin}ich/denn 
-True if file exists and its set-group-id bit is set.  + 
--h file  +Quoting: 
-True if file exists and is a symbolic link.  +bei echo '$x' kommt raus: $x 
--k file  + 
-True if file exists and its "sticky" bit is set.  +bei echo "$x" kommt raus: hallo 
--p file  + 
-True if file exists and is a named pipe (FIFO).  +" interpretiert Variablen, 
--r file  +' tut das nicht! (sondern 'wörtlich') 
-True if file exists and is readable.  + 
--s file  +parameter /variables substitution: 
-True if file exists and has a size greater than zero.  +http://www.unet.univie.ac.at/aix/aixuser/usrosdev/parameter_subst.htm#AC8A8CF676shar
--t fd  +
-True if file descriptor fd is open and refers to a terminal.  +
--u file  +
-True if file exists and its set-user-id bit is set.  +
--w file  +
-True if file exists and is writable.  +
--x file  +
-True if file exists and is executable.  +
--O file  +
-True if file exists and is owned by the effective user id.  +
--G file  +
-True if file exists and is owned by the effective group id.  +
--L file  +
-True if file exists and is a symbolic link.  +
--S file  +
-True if file exists and is a socket.  +
--N file  +
-True if file exists and has been modified since it was last read.  +
-file1 -nt file2  +
-True if file1 is newer (according to modification date) than file2.  +
-file1 -ot file2  +
-True if file1 is older than file2.  +
-file1 -ef file2  +
-True if file1 and file2 have the same device and inode numbers.  +
--o optname  +
-True if shell option optname is enabled. The list of options appears in the description of the `-o' option to the set builtin (see section 4.3 The Set Builtin).  +
--z string  +
-True if the length of string is zero.  +
--n string  +
-string  +
-True if the length of string is non-zero.  +
-string1 == string2  +
-True if the strings are equal. `=' may be used in place of `=='.  +
-string1 != string2  +
-True if the strings are not equal.  +
-string1 < string2  +
-True if string1 sorts before string2 lexicographically in the current locale.  +
-string1 > string2  +
-True if string1 sorts after string2 lexicographically in the current locale.  +
-arg1 OP arg2  +
-OP is one of `-eq', `-ne', `-lt', `-le', `-gt', or `-ge'. These arithmetic binary operators return true if arg1 is equal to, not equal to, less than, less than or equal to, greater than, or greater than or equal to arg2, respectively. Arg1 and arg2 may be positive or negative integers.+
  
 nette einfhrung: nette einfhrung:
Zeile 159: Zeile 67:
  
 Werte eines Files in Veriablen einlesen Werte eines Files in Veriablen einlesen
-Achtung: Dieses Skript liest wortweise ein (Leerzeichen getrennt) und ignoriert Leerzeichen/Leerzeilen+Achtung: Dieses Skript liest wortweise ein (Leerzeichen getrennt) und ignoriert 
 +Leerzeichen/Leerzeilen 
 + 
 +<code bash>
 #!/bin/sh #!/bin/sh
 ISOPATH=/data1/iso ISOPATH=/data1/iso
Zeile 177: Zeile 88:
 done done
 exit 0 exit 0
 +</code>
  
-Datei zeile fr zeile lesen: script <datei +Datei zeile für zeile lesen:  
-> while [ true ] +<code bash> 
-> do +script <datei 
->         read X  #read a line +while [ true ] 
->         if [ $? -ne 0 ] #Break if EOF + do 
->         then +         read X  #read a line 
->                 break +         if [ $? -ne 0 ] #Break if EOF 
->         fi +         then 
->         echo $X #Your action goes here. +                 break 
-> done < tmp.txt+         fi 
 +         echo $X #Your action goes here. 
 + done < tmp.txt 
 +</code>
  
 gut: gut:
-http://steve-parker.org/sh/bourne.html+ 
 +[[http://steve-parker.org/sh/bourne.html]]
 
Nach oben
shell.1208875091.txt.gz · Zuletzt geändert: 2024/02/29 13:35 (Externe Bearbeitung)
Übersicht Letzte Änderungen
Admin
chimeric.de = chi`s home Creative Commons License Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0
DFmW2CEce3htPL1uNQuHUVu4Tk6WXigFQp   Dogecoin Donations Accepted Here    DFmW2CEce3htPL1uNQuHUVu4Tk6WXigFQp  DFmW2CEce3htPL1uNQuHUVu4Tk6WXigFQp