Book Image

Bash Cookbook

By : Ron Brash, Ganesh Sanjiv Naik
Book Image

Bash Cookbook

By: Ron Brash, Ganesh Sanjiv Naik

Overview of this book

In Linux, one of the most commonly used and most powerful tools is the Bash shell. With its collection of engaging recipes, Bash Cookbook takes you through a series of exercises designed to teach you how to effectively use the Bash shell in order to create and execute your own scripts. The book starts by introducing you to the basics of using the Bash shell, also teaching you the fundamentals of generating any input from a command. With the help of a number of exercises, you will get to grips with the automation of daily tasks for sysadmins and power users. Once you have a hands-on understanding of the subject, you will move on to exploring more advanced projects that can solve real-world problems comprehensively on a Linux system. In addition to this, you will discover projects such as creating an application with a menu, beginning scripts on startup, parsing and displaying human-readable information, and executing remote commands with authentication using self-generated Secure Shell (SSH) keys. By the end of this book, you will have gained significant experience of solving real-world problems, from automating routine tasks to managing your systems and creating your own scripts.
Table of Contents (15 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Introduction


This chapter is about creating components that mimic application functionality such as menus or a daemon. For that to happen, let's step back for a second and determine: what defines an application or daemon? Is it menus? Is it the ability to run forever? Or the ability to run headless in the background? All of this defines behaviors that an application may exhibit, but nothing prevents a script from also having these behaviors as well!

For example, if a bash script did not have an extension (for example, .sh) and was not ran explicitly with the Bash interpreter, how would you know on the first inspection that it was a script and not a binary? While there are a number of ways such as opening, or using the file command, on the surface, a script can appear the same as a program!