Search Results

Screen is probably what you are looking for: https://www.unix.com/man-page/redhat/1/screen/ (https://www.unix.com/man-page/redhat/1/screen/)

Busybox uses its own implementation of awk, seemingly one that uses null-terminated strings internally (as opposed to length prefixed, which could handle null characters inside strings). I used...

Separating the substitutions works:

awk 'NR>1 { if ($2 ~ /^\(/ ) {$1=""; print "Found error: ", $0} else { sub(/.*:/, "", $1); sub(/.*:/, "", $7); print "No error: " $1 "," $7}}'...

You want to prepend an echo on the last line ...

You could go by the file date of /var/sadm/patch/*/log . For patches that came pre-installed something like grep -h PATCH_INFO /var/sadm/pkg/SUNW*/pkginfo will get you the information.

Using set/shift will work:

names1="cdb1 cdb2 cdb3"
names2="pdb1 pdb2 pdb3"

set $names2
for name in $names1; do
export DB=$name
export PDB=$1
shift
echo "$DB:$PDB"
done

For some reason the MAIL variable seems to be wrong. Are you using "su" instead of "su -" to change from root to the user? If not I would check the various profile/rc files that set those variables...

Find itself can test for non-empty files, in an if test this could look like:

if [ -n "`find /path/FTP. -type f -size +0`" ]; then sleep 28800; fi

grep "$A"'\>' *should do the trick: double quotes to allow expanding of $A, single ones for the rest.

edit: of course just using double quotes will do too:

grep "$A\>" *

That is because $ would match end of line and not end of string. Depending on the exact nature of the input you could match for space/tab instead, or just not a letter:

sed -n '1,/^LAC[^a-zA-Z]/p'...

This may be an anti-spam measure on the receiving side, trying stuff like doing a reverse-lookup on your IP.

What I was trying to say is, that it is probably not mailx taking the time, but the receiving server not responding earlier for whatever reason. If you don't have access to the server it may be out...

And probably after a while the "220" line. I just see hat there is a nifty telnet-ssl package too, so you can verify that it isn't mailx causing the delays with port 465 .

Something along the following might help

No more than one x:
grep -v "x.*x" .location/*.txtExactly one x:
grep x .location/*.txt|grep -v "x.*x"

So according the docs you would expect 12 cores? Can you verify this in the bios?

Anyway, you could check if it is a case of cores being offline to save power:

cat...

Something like the following might do for an overview:
sed 's/,[ ]*/\n/g' flugent.txt |comm - IDT.txtOr
sed 's/,[ ]*/\n/g' flugent.txt |comm -12 - IDT.txtfor the matching list.

Just doing something like grep "\(Thread\|SESSION DESCRIPTION\)" test.xml may help, then dealing with a simpler stream containing only those lines.