{"id":191,"date":"2018-10-17T00:00:00","date_gmt":"2018-10-16T16:00:00","guid":{"rendered":"https:\/\/yeslq.com\/201810191.html"},"modified":"2019-05-07T10:43:29","modified_gmt":"2019-05-07T02:43:29","slug":"the-linux-command-line-command","status":"publish","type":"post","link":"https:\/\/yeslq.com\/?p=191","title":{"rendered":"The Linux Command Line—Command Substitution And Constants"},"content":{"rendered":"

\nThe Linux Command Line <\/a><\/i>by William Shotts<\/span><\/h1>\n
\n
<\/span><\/div>\n
\n<\/span><\/p>\n
\nIn the previous lesson, we learned how to create variables and perform expansions with them. In this lesson, we will extend this idea to show how we can substitute the results from a command.<\/span><\/div>\n


\n<\/span><\/p>\n

\nWhen we last left our script, it could create an HTML page that contained a few simple lines of text, including the host name of the machine which we obtained from the environment variable HOSTNAME. Now, we will add a time stamp to the page to indicate when it was last updated, along with the user that did it.<\/span><\/div>\n

<\/p>\n

\n
#!\/bin\/bash\n\n# sysinfo_page - A script to produce an HTML file\n\ntitle=\"System Information for\"\n\ncat <<- _EOF_\n    <html>\n    <head>\n        <title>\n        $title $HOSTNAME\n        <\/title>\n    <\/head>\n\n    <body>\n    <h1>$title $HOSTNAME<\/h1>\n    <p>Updated on $(date +\"%x %r %Z\") by $USER<\/p>\n    <\/body>\n    <\/html>\n_EOF_\n       \n<\/pre>\n<\/div>\n
\nAs you can see, we employed another environment variable, USER, to get the user name. In addition, we used this strange looking thing:<\/div>\n
\n$(date +”%x %r %Z”)<\/div>\n
\nThe characters “$( )” tell the shell, “substitute the results of the enclosed command.” In our script, we want the shell to insert the results of the command date +”%x %r %Z” which expresses the current date and time. The date<\/a> command has many features and formatting options. To look at them all, try this:<\/div>\n
\n[me@linuxbox me]$ date –help | less<\/div>\n
\nBe aware that there is an older, alternate syntax for “$(command)” that uses the backtick character ” ` “. This older form is compatible with the original Bourne shell (sh). I tend not to use the older form since I am teaching modern bash here, not sh, and besides, I think backticks are ugly. The bash shell fully supports scripts written for sh, so the following forms are equivalent:<\/div>\n
\n$(command)
`command`<\/div>\n
\nAssigning A Command’s Result To A Variable<\/h2>\n
\nYou can also assign the results of a command to a variable:<\/div>\n
\nright_now=$(date +”%x %r %Z”)<\/div>\n
\nYou can even nest the variables (place one inside another), like this:<\/div>\n
\nright_now=$(date +”%x %r %Z”)
time_stamp=”Updated on $right_now by $USER”<\/div>\n
\nConstants<\/h2>\n
\nAs the name variable suggests, the content of a variable is subject to change. This means that it is expected that during the execution of your script, a variable may have its content modified by something you do.<\/div>\n
\nOn the other hand, there may be values that, once set, should never be changed. These are calledconstants<\/i>. I bring this up because it is a common idea in programming. Most programming languages have special facilities to support values that are not allowed to change. Bash also has these facilities but, to be honest, I never see it used. Instead, if a value is intended to be a constant, it is given an uppercase name to remind the programmer that it should be considered a constant even if it’s not being enforced.<\/div>\n
\nEnvironment variables are usually considered constants since they are rarely changed. Like constants, environment variables are given uppercase names by convention. In the scripts that follow, I will use this convention – uppercase names for constants and lowercase names for variables.<\/div>\n
\nSo with everything we know, our program looks like this:<\/div>\n
\n
#!\/bin\/bash\n\n# sysinfo_page - A script to produce an HTML file\n\ntitle=\"System Information for $HOSTNAME\"\nRIGHT_NOW=$(date +\"%x %r %Z\")\nTIME_STAMP=\"Updated on $RIGHT_NOW by $USER\"\n\ncat <<- _EOF_\n    <html>\n    <head>\n        <title>\n        $title\n        <\/title>\n    <\/head>\n\n    <body>\n    <h1>$title<\/h1>\n    <p>$TIME_STAMP<\/p>\n    <\/body>\n    <\/html>\n_EOF_\n       \n<\/pre>\n<\/div>\n
\n<\/div>\n
<\/span><\/div>\n","protected":false},"excerpt":{"rendered":"
The Linux Command Line by William Shotts In the pr … \u9605\u8bfb\u66f4\u591a<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[51,52,53],"class_list":["post-191","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-linux","tag-shell","tag-the-linux-command-line"],"_links":{"self":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/191","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=191"}],"version-history":[{"count":1,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/191\/revisions"}],"predecessor-version":[{"id":313,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/191\/revisions\/313"}],"wp:attachment":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=191"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=191"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=191"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}