Search Results

If you have the output in a variable, you don't need any external command:

output='Device "nrst3a" attributes=(0x4) RAW SERIAL_NUMBER=SN[VD073AV1443BVW00083]L2'

IFS=\" read a s1 b <<<...

s/crippled/standard/

awk 'BEGIN { print "<div align=center>" }
{ gsub(/&/,"&amp;"); gsub(/</,"&lt;") }
/^$/ { print; last = "blank"; next }
last == "blank" || NR == 1 {
last = ""
printf " <p>"
}
/THE DISTRICT COURT...

That will only work with the GNU date command; -d is not standard.



I doubt that OP is using a system without a POSIX shell, so there's no need for cut:

IFS=/ read month day year whatever...

That will fail if $AllFile contains whitespace.

}' "$AllFile.tmp" > "$AllFile"

Do not use basename. It is an external command that is an order of magnitude slower than using the shell's parameter expansion.

That is almost almost always the wrong way ro read the contents of a file. Not only is cat unnecssary but it will break your script if any lines contain whitespace or other pathological characters....

With bash there is no need for any external command:


#!/bin/bash
file=$1

mapfile -t xx < "$file"
n=${#xx[@]}
printf "%s\n" "${xx[@]:1:n-2}"

The best places I have found are this forum and the Usenet newsgroup comp.unix.shell.

First, you don't need -1 when the output of ls is not going to a terminal.

Second, the command will fail if $1 contains whitespace or other pathological characters.

Third, there is no need for...

man bash:"Redirections using file descriptors greater than 9 should be used with care, as they may conflict with file descriptors the shell uses internally."

Rather than whereis, use type; It tells you what the shell will actually use:


$ type [
[ is a shell builtin


With the -a option, it gives all the possible commands that could be executed:
...

There is no need to use an external command for integer arithmetic in bash (or any other POSIX shell):

count=$(( count + 1 ))


Or, in bash:


(( ++count ))

If you want to get a value from the command line, use the positional parameters, $1, etc., not 'read'.


case $1 in
1|memory) echo " you've selected check memory..1 sec pls "
...

grep "^$acc;" "$file"

There's no point in sourcing the script if you are putting it in the background.

A background process is not executed in the current shell.

There should be no space after file, and you don't need both $( ... ) and ` ... `.

date=$(date +%Y%m%d)
file=$(find . -name "$date"_*.xml)
mv "$file" renamedfeed_"$date".xml

## NAME: topntail
## USAGE: topntail [-b N] [-e N] [FILE ...]

b=1 ## No. of lines to remove from beginning
e=1 ## No. of lines to remove from end

## Parse command-line options
while...

Please convert the DOC file to a TXT file. I'm not going to load OpenOffice just for that.

Use the format specifiers to get whatever output you want. For example:

date +%y%m%d

See the man page for the full list of specifiers.

awk '/^processor/ { processor = $0 }
/^model name/ { print processor, $0 }
' /proc/cpuinfo

I'll leave the removal of "model name :" to you.

There is nothing in the script that is specifically bash other than ==; = works just as well and is portable.

Put code inside [CODE] tags, not [QUOTE] tags.

(You can edit your post to fix it.)

#!/bin/bash

usage="${0##*/} SERVER USER PASSWORD [PORT]"

case $1 in
-*|"") printf "USAGE: %s\n" "$usage"; exit ;;
esac

host=${1:-mail.example.com}
user=${2:-poppy}...

logfile=backup_every_hour_script.log
{
rsync -auv "$dir" "$backup_dir"
cat "$logfile"
} > tmpfile
mv tmpfile "$logfile"