Unix Commands Quick ReferenceUseful commands and flags that we get tired of looking up... | ||||||||
Changed: | ||||||||
< < | Disk Space | |||||||
> > | Disk Space | |||||||
The du command is verbose and confusing if you run it without options. Here is how to get a human-readable output and a grand total for the path argument (omit for current directory).
du -hc | ||||||||
Changed: | ||||||||
< < | Fixing Line Endings | |||||||
> > | Fixing Line Endings | |||||||
If you get odd errors after transferring a text file from a PC or Mac to a Unix machine, it's likely that you have a problem with newline characters. This is especially common when editing files in Excel and saving them to tab-delimited or comma-delimited files for input into. You can generally avoid this problem and fix the line endings by using an industrial strength text editor. This command converts Mac line endings in a saved Excel file to Unix line endings.
tr "\r" "\n" < input.tab >.converted.tab
Merging commands to be serial on TACCSometimes you have 96 short jobs that you want to run serially 8 at a time on 12 cores rather than requesting 96 cores. This command will combine every 8 lines in a file into one line separated by && so that these commands are now run on one core.paste -s -d'#######\n' commands | sed "s/#/ \&\& /g" > commands8 | ||||||||
Added: | ||||||||
> > |
Adding your path to the command promptAdd to your.bashrc or similar bash startup script:
export PS1='\w\$ ' |