Skip to content

Latest commit

 

History

History
174 lines (88 loc) · 4.06 KB

awk_statistics.md

File metadata and controls

174 lines (88 loc) · 4.06 KB
layout title tags
manual
awk - Statistics of command combinations using double pipe
statistic

Before

The commands before awk: If the given command failed, execute awk.

Command percentage
free 25%
awk 25%
w 25%
ss 25%

After

The commands after awk: If awk failed, execute the given command.

Command Percentage
echo 9%
sed 9%
ss 9%
grep 4%
cp 4%
man 4%
awk 4%
w 4%
uptime 4%
sleep 4%
comm 4%
bc 4%
ssh 4%
cal 4%
nohup 4%
host 4%
sudo 4%
su 4%
ip 4%

Related Scenarios

Below are the scenarios for all command combinations above.

The description in the table is referenced from and can be used to search the one-line-command or the scripts in the website of CommandLineFu.

If free failed, execute awk

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If awk failed, execute awk

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If w failed, execute awk

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If ss failed, execute awk

  • Lookup autonomous systems of all outgoing http/s traffic

If awk failed, execute echo

  • delay execution of a command that needs lots of memory and CPU time until the resources are available
  • Check CRL expiration time

If awk failed, execute sed

  • delay execution of a command that needs lots of memory and CPU time until the resources are available
  • Find Duplicate Files (based on size first, then MD5 hash)

If awk failed, execute ss

  • delay execution of a command that needs lots of memory and CPU time until the resources are available
  • ensure your ssh tunnel will always be up (add in crontab)

If awk failed, execute grep

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If awk failed, execute cp

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If awk failed, execute man

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If awk failed, execute awk

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If awk failed, execute w

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If awk failed, execute uptime

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If awk failed, execute sleep

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If awk failed, execute comm

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If awk failed, execute bc

  • delay execution of a command that needs lots of memory and CPU time until the resources are available

If awk failed, execute ssh

  • ensure your ssh tunnel will always be up (add in crontab)

If awk failed, execute cal

  • ensure your ssh tunnel will always be up (add in crontab)

If awk failed, execute nohup

  • ensure your ssh tunnel will always be up (add in crontab)

If awk failed, execute host

  • ensure your ssh tunnel will always be up (add in crontab)

If awk failed, execute sudo

  • Block all FaceBook traffic

If awk failed, execute su

  • Block all FaceBook traffic

If awk failed, execute ip

  • Block all FaceBook traffic