<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why did the lookup file not move despite changing its read perms? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Why-did-the-lookup-file-not-move-despite-changing-its-read-perms/m-p/296850#M89544</link>
    <description>&lt;P&gt;I have noticed this as well, actually! I am not sure why it does that, exactly, but my best suggestion would be to submit a ticket to Splunk. That's what I did &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Maybe it'll be fixed in a new release. &lt;/P&gt;</description>
    <pubDate>Thu, 29 Mar 2018 11:42:40 GMT</pubDate>
    <dc:creator>cmerriman</dc:creator>
    <dc:date>2018-03-29T11:42:40Z</dc:date>
    <item>
      <title>Why did the lookup file not move despite changing its read perms?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-did-the-lookup-file-not-move-despite-changing-its-read-perms/m-p/296849#M89543</link>
      <description>&lt;P&gt;I changed the permissions on a lookup file from the UI via Manage Apps - &amp;gt; Search and Reporting -&amp;gt; View Objects -&amp;gt; Read access to everyone on the lookup object. However, on my search head the lookup file is still under $SPLUNK_HOME/etc/users//search/lookups and not under $SPLUNK_HOME/etc/apps/search/lookups/. The read access has been given on app level but at the backend, the file still remains in the user directory. rendering it inaccessible. Is this a bug with Splunk?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 18:44:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-did-the-lookup-file-not-move-despite-changing-its-read-perms/m-p/296849#M89543</guid>
      <dc:creator>sarahafrin</dc:creator>
      <dc:date>2020-09-29T18:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: Why did the lookup file not move despite changing its read perms?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Why-did-the-lookup-file-not-move-despite-changing-its-read-perms/m-p/296850#M89544</link>
      <description>&lt;P&gt;I have noticed this as well, actually! I am not sure why it does that, exactly, but my best suggestion would be to submit a ticket to Splunk. That's what I did &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Maybe it'll be fixed in a new release. &lt;/P&gt;</description>
      <pubDate>Thu, 29 Mar 2018 11:42:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Why-did-the-lookup-file-not-move-despite-changing-its-read-perms/m-p/296850#M89544</guid>
      <dc:creator>cmerriman</dc:creator>
      <dc:date>2018-03-29T11:42:40Z</dc:date>
    </item>
  </channel>
</rss>

