<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Troubleshooting on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/troubleshooting/</link>
    <description>Recent content in Troubleshooting on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 16 May 2026 08:11:30 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/troubleshooting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Troubleshooting Permission Issues with Default Umask and ACLs in Shared Directories</title>
      <link>https://linuxeries.org/post/2026-05-16-troubleshooting-permission-issues-with-defaul/</link>
      <pubDate>Sat, 16 May 2026 08:11:30 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-05-16-troubleshooting-permission-issues-with-defaul/</guid>
      <description>&lt;h2 id=&#34;introduction-to-umask-and-acls&#34;&gt;Introduction to Umask and ACLs&lt;/h2&gt;&#xA;&lt;p&gt;When working with shared directories in Linux, I&amp;rsquo;ve seen permission issues arise due to the default umask and Access Control Lists (ACLs). The real trick is understanding how these two settings interact. The umask is a 3-digit octal number that determines the default permissions for newly created files and directories, while ACLs provide a more fine-grained access control mechanism.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-umask&#34;&gt;Understanding Umask&lt;/h2&gt;&#xA;&lt;p&gt;The umask is subtracted from the maximum possible permissions (777 for directories and 666 for files) to determine the default permissions. For example, a umask of 022 would result in default permissions of 755 for directories (777 - 022 = 755) and 644 for files (666 - 022 = 644). To view the current umask, you can use the &lt;code&gt;umask&lt;/code&gt; command:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
