<?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 vmunix: Remote property list daemon not registered in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/vmunix-remote-property-list-daemon-not-registered/m-p/3494985#M12134</link>
    <description>Can anyone offer up some insight as to what might be causing this message to be reported frequently in the kern log. We have a tru64 unix box that mounts a directory on a windows server that is running MS Windows Services For Unix v3.5&lt;BR /&gt;&lt;BR /&gt;Thanks for any pointers. The message could be just informational, as it is not causing any problems.</description>
    <pubDate>Tue, 01 Mar 2005 05:21:16 GMT</pubDate>
    <dc:creator>Stuart Green</dc:creator>
    <dc:date>2005-03-01T05:21:16Z</dc:date>
    <item>
      <title>vmunix: Remote property list daemon not registered</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/vmunix-remote-property-list-daemon-not-registered/m-p/3494985#M12134</link>
      <description>Can anyone offer up some insight as to what might be causing this message to be reported frequently in the kern log. We have a tru64 unix box that mounts a directory on a windows server that is running MS Windows Services For Unix v3.5&lt;BR /&gt;&lt;BR /&gt;Thanks for any pointers. The message could be just informational, as it is not causing any problems.</description>
      <pubDate>Tue, 01 Mar 2005 05:21:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/vmunix-remote-property-list-daemon-not-registered/m-p/3494985#M12134</guid>
      <dc:creator>Stuart Green</dc:creator>
      <dc:date>2005-03-01T05:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: Remote property list daemon not registered</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/vmunix-remote-property-list-daemon-not-registered/m-p/3494986#M12135</link>
      <description>&lt;BR /&gt;Stu,&lt;BR /&gt;&lt;BR /&gt;To stop this message, do:&lt;BR /&gt;&lt;BR /&gt;rcmgr set NUM_PROPLISTD 1&lt;BR /&gt;/usr/sbin/proplistd 1&lt;BR /&gt;&lt;BR /&gt;Next time you start the system, the proplistd will be auto-started.&lt;BR /&gt;&lt;BR /&gt;The correct way to set this up is via nfssetup. The proplist daemon is used to handle extended file attributes (like ACL's)&lt;BR /&gt;&lt;BR /&gt;__ Johan.</description>
      <pubDate>Tue, 01 Mar 2005 10:33:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/vmunix-remote-property-list-daemon-not-registered/m-p/3494986#M12135</guid>
      <dc:creator>Johan Brusche</dc:creator>
      <dc:date>2005-03-01T10:33:37Z</dc:date>
    </item>
  </channel>
</rss>

