Stop hacking the filesystem just to handle group inheritance
Permissions & Security (Chmod/Chown/ACLs/SELinux/AppArmor)
Stop hacking the filesystem just to handle group inheritance
🧩 The Challenge
Setting up a shared directory for a dev team used to mean constant chmod -R and praying nobody forgot to set the right group. It’s a nightmare trying to keep files accessible when the default umask is busy ruining your day.
💡 The Fix
You should be using setgid bits on your directories instead of fighting with cron jobs or manual fix-ups. This ensures every new file created in a folder automatically inherits the directory’s group ownership.
chmod g+s /path/to/shared/directory
⚙️ Why It Works
Setting the setgid bit on a directory forces the effective group ID of new files to match the parent directory’s group, rather than the user’s primary group. It’s the easiest way to keep team folders sane without installing complex ACLs.
🚀 Pro-Tip: Throw a sticky bit on there with chmod +t if you want to prevent users from deleting files they don’t own.
Linux Tips & Tricks | © ngelinux.com | 11/7/2026
