4 ms·
Ask HN: What are your top most useful Unix commands?
- chmielewski 7y agotime cat
- apotatopot 7y agotop jk, but also not. w !sudo tee % in vim, even tho that's not really directly a unix thing?
- hntddt1 7y agols
- 0x445442 7y agodirs -v pushd popd
- wbsun 7y agocd pwd ls
- jjjbokma 7y agofind, grep
- antoineMoPa 7y agogrep, find, tail -f (useful to look at log files as they update) Extras: sort, uniq, sed, sftp, apropos, man
- jjjbokma 7y agotail -F This will also follow a log file if it rotates.
- jolmg 7y agoI 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: pstree -p $(pgrep -o apache2) \ | grep -Po '[^}]\(\K\d+' | sed ':b;N;$!bb;s/\n/,/g' \ | sudo xargs lsof -d 0-1000 -a -p \ | grep -Po '\S+$' \ | grep 'log' \ | sort -u \ | xargs tail -F
- potta_coffee 7y agohistory | grep <command halfway remember using>
- sgillen 7y agoemacs&
- kleer001 7y agothe semicolon ";" for chaining commands ls -l the "alias" command in a file for setting up quick-commands
- runjake 7y agocut, awk, sed, comm, grep
- jolmg 7y agogit
- simonblack 7y agols, find, grep, tar, cpio But in truth, it's the bash scripting 'glue' that holds everything together.
- DrScump 7y agokill lets you send any signal to a process you have control over. Corresponding signal handlers allow a wide range of behavior changes.
- ksaj 7y agoA 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.