Differences between revisions 11 and 18 (spanning 7 versions)
Revision 11 as of 2007-11-22 06:51:01
Size: 1887
Editor: pgas
Comment:
Revision 18 as of 2007-12-12 02:48:58
Size: 2045
Editor: GreyCat
Comment: minor spelling fix/clarification
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
If you want to see if you can read, write or execute a file, there is test -r, -x and -w.
Line 12: Line 14:
 * On GNU/Linux systems, and possibly others, there is a command called `stat(1)`. On older GNU/Linux systems, this command take no options -- just a filename -- and you will have to parse its output.  * On GNU/Linux systems, *BSD and possibly others, there is a command called `stat(1)`. On older GNU/Linux systems, this command take no options -- just a filename -- and you will have to parse its output.
Line 23: Line 25:
 * On newer GNU/Linux systems, the `stat` command takes arguments which allow you to specify which information you want:  * On newer GNU/Linux and FreeBSD systems, the `stat` command takes arguments which allow you to specify which information you want:
Line 26: Line 28:
 That's obviously a lot easier to parse.  That's obviously a lot easier to parse.  (NetBSD and OpenBSD use `-f` instead of `-c`.)

Anchor(faq87)

How can I get the permissions of a file without parsing ls -l output?

There are several potential ways, most of which are system-specific. They also depend on precisely why you want the permissions.

The majority of the cases where you might ask this question -- such as I want to find any files with the setuid bit set -- can be answered by the information in [:UsingFind#permissions:]. As the page name implies, those answers are based on the find(1) command.

For some questions, such as I want to make sure this file has 0644 permissions, you don't actually need to check what the permissions are. You can just use chmod 0644 myfile and set them directly.

If you want to see if you can read, write or execute a file, there is test -r, -x and -w.

If your needs aren't met by any of those, then we can look at a few alternatives:

  • On GNU/Linux systems, *BSD and possibly others, there is a command called stat(1). On older GNU/Linux systems, this command take no options -- just a filename -- and you will have to parse its output. {{{$ stat /

    • File: "/" Size: 1024 Filetype: Directory Mode: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
    Device: 8,0 Inode: 2 Links: 25 Access: Wed Oct 17 14:58:02 2007(00000.00:00:01) Modify: Wed Feb 28 15:42:14 2007(00230.22:15:49) Change: Wed Feb 28 15:42:14 2007(00230.22:15:49)}}}

    In this case, one could extract the 0755 from the Mode: line, using awk or similar commands.

  • On newer GNU/Linux and FreeBSD systems, the stat command takes arguments which allow you to specify which information you want: {{{$ stat -c %a / 755}}} That's obviously a lot easier to parse. (NetBSD and OpenBSD use -f instead of -c.)

  • On systems with perl 5, you can use:
     perl -e 'printf "%o\n", 07777 & (stat $ARGV[0])[2]' "$filename"

    This returns the same octal string that the stat -c %a example does, but is far more portable. (And slower.)

BashFAQ/087 (last edited 2015-09-28 19:14:40 by GreyCat)