{"id":19212,"date":"2010-05-28T08:09:27","date_gmt":"2010-05-28T08:09:27","guid":{"rendered":"http:\/\/euvolution.com\/futurist-transhuman-news-blog\/unix-sysadmin-boot-camp-bash\/"},"modified":"2010-05-28T08:09:27","modified_gmt":"2010-05-28T08:09:27","slug":"unix-sysadmin-boot-camp-bash","status":"publish","type":"post","link":"https:\/\/www.euvolution.com\/futurist-transhuman-news-blog\/planetology\/unix-sysadmin-boot-camp-bash.php","title":{"rendered":"UNIX Sysadmin Boot Camp: bash"},"content":{"rendered":"

\"RyanWelcome back to UNIX Sysadmin Boot Camp<\/a>. You’ve had a few days to get some “reps” in accessing your server via SSH<\/a>, so it’s about time we add some weight to your exercise by teaching you some of the tools you will be using regularly to manage your server.<\/p>

As we mentioned earlier in this series, customers with control panels like cPanel\/WHM and Plesk might be tempted to rely solely on those graphical interfaces. They are much more user-friendly in terms of performing routine server administration tasks, but at some point, you’re going to need to get down and dirty on the command line. It’s inevitable. This is where you’ll use bash<\/strong> commands. <\/p>

Here are some of the top 10 essential commands you should get to know and remember in bash. Click any of the commands to go to its official “manual” page.<\/em><\/p>

  1. man<\/code><\/a> – This command provides a manual of other bash commands. Want more info on a command? Type man commandname<\/code>, and you’ll get more information about “commandname” than you probably wanted to know. It’s extremely useful if you need a quick reference for a command, and it’s often much more detailed and readable than a simple --help<\/code> or --h<\/code> extension.<\/li>
  2. ls<\/code><\/a> – This command lets you list results. I showed you an example of this above, but the amount of options that are available to you with this command are worth looking into. Using the “manual” command above, run man ls<\/code> and check out the possibilities. For example, if you’re in \/etc<\/code>, running ls –l \/etc<\/code> will get you a slightly more detailed list. My most commonly used list command is ls –hal<\/code>. Pop quiz for you (where you can test your man<\/code> skills): What does the -hal<\/code> mean?<\/li>
  3. cd<\/code><\/a> – This command lets you change directories. Want to go to \/etc\/<\/code>? cd \/etc\/<\/code> will take you there. Want to jump back a directory? cd ..<\/code> does the trick.<\/li>
  4. mv<\/code><\/a> – This command enables you to move files and folders. The syntax is mv originalpath\/to\/file newpath\/to\/file<\/code>. Simple! There are more options that you can check out with the man<\/code> command.<\/li>
  5. rm<\/code><\/a> – This command enables you to remove a file or directory. In the same vein as the mv<\/code> command, this is one of those basic commands that you just have to know. By running rm filename<\/code>, you remove the “filename” file.<\/li>
  6. cp<\/code><\/a> – This command enables you to copy files from one place to another. Want to make a backup of a file before editing it? Run cp origfile.bla origfile.bak<\/code>, and you have a backup in case your edit of origfile.bla<\/code> goes horrendously wrong and makes babies cry. The syntax is simply: cp \/source \/destination<\/code>. As with the above commands, check out the manual by running man cp<\/code> for more options.<\/li>
  7. tar<\/code><\/a> – On its own, tar<\/code> is a command to group a bunch of files together, uncompressed. These files can then be compressed into .gzip format. The command can be used for creating or extracting, so it may be a good idea to familiarize yourself with the parameters, as you may find yourself using it quite often. For a GUI equivalent, think 7-zip or WinRAR for Windows.<\/li>
  8. wget<\/code><\/a> – I love the simplicity of this little command. It enables you to “get” or download a target file. Yes, there are options, but all you need is a direct link to a file, and you just pull one of these: wget urlhere<\/code>. Bam! That file starts downloading. Doesn’t matter what kind of file it is, it’s downloaded.<\/li>
  9. top<\/code><\/a> – This handy little binary will give you a live view of memory and CPU usage currently affecting your machine, and is useful for finding out where you need to optimize. It can also help you pinpoint what processes may be causing a slowdown or a load issue.<\/li>
  10. chmod<\/code><\/a> – This little sucker is vital to make your server both secure and usable, particularly when you’re going to be serving for the public like you would with a web server. If you read about how I learned to stop worrying and love the bomb, er permissions<\/a>, you should be familiar with this command and its connotations. Combine good usage of permission and iptables, and you have a locked down server<\/li><\/ol>

    When you understand how to use these tools, you can start to monitor and track what’s actually happening on your server. The more you know about your server, the more effective and efficient you can make it. In our next installment, we’ll touch on some of the most common server logs and what you can do with the information they provide.<\/p>

    Did I miss any of your “essential” bash commands in my top 10 list? Leave a comment below with your favorites along with a quick explanation of what they do.<\/p>

    -Ryan<\/p>

    Related Posts:<\/h4>