<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Comments on snippet: 'Chmod files recursively to 644'</title>
    <description>Snipplr comments feed</description>
    <link>https://ipv6.snipplr.com/</link>
    <lastBuildDate>Wed, 15 Apr 2026 00:09:54 +0000</lastBuildDate>
    <item>
      <title>laforge said on 14/Oct/2010</title>
      <link>https://ipv6.snipplr.com/view/42216/chmod-files-recursively-to-644</link>
      <description>&lt;p&gt;You can try directly this:&#13;
&#13;
find . -type f -exec chmod 644 '{}' \;&lt;/p&gt;</description>
      <pubDate>Thu, 14 Oct 2010 03:44:16 UTC</pubDate>
      <guid>https://ipv6.snipplr.com/view/42216/chmod-files-recursively-to-644</guid>
    </item>
    <item>
      <title>jfine said on 24/May/2012</title>
      <link>https://ipv6.snipplr.com/view/42216/chmod-files-recursively-to-644</link>
      <description>&lt;p&gt;That would work unless there are some really wacky filenames. That's the main reason I'm using the -print0 pattern.&#13;
&#13;
See this URL for more info:&#13;
http://www.gnu.org/software/findutils/manual/html_node/find_html/Problems-with-_002dexec-and-filenames.html&lt;/p&gt;</description>
      <pubDate>Thu, 24 May 2012 06:48:05 UTC</pubDate>
      <guid>https://ipv6.snipplr.com/view/42216/chmod-files-recursively-to-644</guid>
    </item>
  </channel>
</rss>
