kill lets you send any signal to a process you have control over. Corresponding signal handlers allow a wide range of behavior changes.
ksaj 1629 days ago [-]
A lot of people only know about its use for literally killing a process. But as an example of where I find myself using it fairly often is:
kill -USR1 <dd>
where <dd> is the process ID (obtained from ps) for the dd command.
Instead of killing dd, it reports back how much has been read/copied so far. Especially useful for working with large files and you decide you want to guestimate how much longer the copy will take.
simonblack 1630 days ago [-]
ls, find, grep, tar, cpio
But in truth, it's the bash scripting 'glue' that holds everything together.
kleer001 1630 days ago [-]
the semicolon ";" for chaining commands
ls -l
the "alias" command in a file for setting up quick-commands
antoineMoPa 1631 days ago [-]
grep, find, tail -f (useful to look at log files as they update)
Extras: sort, uniq, sed, sftp, apropos, man
jjjbokma 1630 days ago [-]
tail -F
This will also follow a log file if it rotates.
jolmg 1630 days ago [-]
I just found out a few days ago that `-F` works with multiple files, too. When there's new content on one, tail prefixes the output with a header, telling you what file it is.
I've used that to watch all logs apache and descendant processes could be writing to:
kill -USR1 <dd>
where <dd> is the process ID (obtained from ps) for the dd command.
Instead of killing dd, it reports back how much has been read/copied so far. Especially useful for working with large files and you decide you want to guestimate how much longer the copy will take.
But in truth, it's the bash scripting 'glue' that holds everything together.
ls -l
the "alias" command in a file for setting up quick-commands
Extras: sort, uniq, sed, sftp, apropos, man
This will also follow a log file if it rotates.
I've used that to watch all logs apache and descendant processes could be writing to:
jk, but also not.
w !sudo tee % in vim, even tho that's not really directly a unix thing?