DE

↑ ↓ select, Enter open, Esc close

Show permissions and owner in octal notation

harmlessPermissions and ownershipalle
Adjust the values, the command updates live
user@server
stat -c '%a %U:%G %n' /var/www/vhosts/example.com/httpdocs/* /var/www/vhosts/example.com/httpdocs/.[!.]*

Prints every file and folder with its permissions in octal notation, owner and group, including hidden files such as .htaccess. Easier to compare than the letter form of ls -l, and the number maps directly to chmod.

Note: If there are no hidden files, stat prints a harmless error for the pattern .[!.]*.

Also searched as

  • show file permissions as number linux
  • find chmod value of a file
  • what permissions does this file have
  • show owner and group

Related one-liners

All in Permissions and ownership

Copy permissions and owner from a reference file

#chmod --reference=/var/www/vhosts/example.com/httpdocs/index.php /var/www/vhosts/example.com/httpdocs/wp-config.php && chown --reference=/var/www/vhosts/example.com/httpdocs/index.php /var/www/vhosts/example.com/httpdocs/wp-config.php
cautionPermissions and ownership

Find world-writable files and directories

$find /var/www/vhosts -xdev -perm -0002 ! -type l -ls 2>/dev/null
harmlessPermissions and ownership

Remove write permission for others recursively

$chmod -R o-w /var/www/vhosts/example.com/httpdocs
cautionPermissions and ownership

Secure the permissions of wp-config.php

$chmod 600 /var/www/vhosts/example.com/httpdocs/wp-config.php
cautionPermissions and ownership

Set all directories to 755 recursively

$find /var/www/vhosts/example.com/httpdocs -type d -exec chmod 755 {} +
cautionPermissions and ownership

Set all files to 644 recursively

$find /var/www/vhosts/example.com/httpdocs -type f -exec chmod 644 {} +
cautionPermissions and ownership

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.