{"id":2888,"date":"2018-02-16T19:04:07","date_gmt":"2018-02-16T16:04:07","guid":{"rendered":"https:\/\/www.howtoforge.com\/linux-stat-command\/"},"modified":"2018-02-16T19:04:07","modified_gmt":"2018-02-16T16:04:07","slug":"linux-stat-command-tutorial-for-beginners-5-examples","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/linux-stat-command-tutorial-for-beginners-5-examples\/","title":{"rendered":"Linux stat Command Tutorial for Beginners (5 Examples)"},"content":{"rendered":"

Sometimes, while working on the command line in Linux, you need to know more about a file. For example, you may want information like file’s size, inode number, access permissions, time of last access or modification, and more. You’ll be glad to know that there exists a command line utility stat<\/strong> that provides all this information in one go.<\/p>\n

In this tutorial, we will discuss the basics of stat using some easy to understand examples. But before we do that, it’s worth mentioning that all examples mentioned here have been tested on Ubuntu 16.04LTS.<\/p>\n

Linux stat command<\/h2>\n

The stat command in Linux allows you to view the status of a file (or even a file system). Here’s the syntax of the command:<\/p>\n

stat [OPTION]… FILE…<\/p>\n

Following are some Q&A-styled examples that will give you a good idea on how stat works.<\/p>\n

Q1. How to use stat command?<\/h2>\n

The tool’s basic usage is very easy – all you have to do is to run the ‘stat’ command with the name of the file you want to know more about.<\/p>\n

stat [filename]<\/p>\n

For example:<\/p>\n

stat test.txt<\/p>\n

\"How<\/a><\/p>\n

So you can see details like file name, size, type of file, access permissions, UIDs and GIDs, as well as Access\/Modify\/Change times.<\/p>\n

Q2. How to make stat display information in terse form?<\/h2>\n

The terse form of output makes it easy for other programs to parse the output. To make ‘stat’ output information in this form, use the -t<\/strong> command line option.<\/p>\n

stat -t test.txt<\/p>\n

\"How<\/a><\/p>\n

Q3. How to make stat output info in custom format?<\/h2>\n

For this, use the –format<\/strong> option. This option requires you to enter a valid format sequence, and a lot of those are available. For example, to access permissions\/rights in human readable form, use %A<\/strong>.<\/p>\n

For example:<\/p>\n

stat –format=%A test.txt<\/p>\n

produces the following output:<\/p>\n

\"How<\/a><\/p>\n

Similarly, you can use %n<\/strong> for file name, %s<\/strong> for size, and %U<\/strong> for user name of the file owner.<\/p>\n

\"Stat<\/a><\/p>\n

Q4. How is –format option different from –printf?<\/h2>\n

At the core, both options do the same thing. The difference lies in the way outputs are produced. While –format<\/strong> outputs a newline after each use, in case of –printf<\/strong>, no newline is added. Here’s how the man page explains both:<\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 -c\u00a0 --format=FORMAT\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 use the specified FORMAT instead of the default; output\u00a0 a\u00a0 new?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 line after each use of FORMAT
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 --printf=FORMAT\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 like\u00a0 --format, but interpret backslash escapes, and do not out?\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 put a mandatory trailing newline; if you want a newline, include\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \\n in FORMAT<\/p><\/pre>\n
Q5. How to make sure stat dereferences in case input file is a link?<\/h2>\n
There’s a dedicated option for this as well: -L<\/strong>. So if the input file is a link, and you want stat to follow it when the command runs, run it in the following way:<\/p>\n
stat -L [filename]<\/p>\n
Conclusion<\/h2>\n
It’d be wrong to say stat<\/em> doesn’t have a learning curve, but the amount of effort the tool demands isn’t much, as the number of command line options it offers are limited. We have already discussed the majority of them here. For more information, head to the tool’s man page<\/a>.<\/p>\n
\n
Share this page:<\/b><\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"
Sometimes, while working on the command line in Linux, you need to know more about a file. For example, you may want information like file’s size, inode number, access permissions, time of last access or modification, and more. You’ll be glad to know that there exists a command line utility stat that provides all this […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-2888","post","type-post","status-publish","format-standard","hentry","category-36"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/2888","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=2888"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/2888\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=2888"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=2888"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=2888"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}