<?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: nfs4cbd listener port number? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/nfs4cbd-listener-port-number/m-p/4771145#M531491</link>
    <description>NFS is going over RPC (remote procedure call)&lt;BR /&gt;&lt;BR /&gt;# rpcinfo -p&lt;BR /&gt;</description>
    <pubDate>Tue, 29 Mar 2011 09:37:41 GMT</pubDate>
    <dc:creator>Viktor Balogh</dc:creator>
    <dc:date>2011-03-29T09:37:41Z</dc:date>
    <item>
      <title>nfs4cbd listener port number?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nfs4cbd-listener-port-number/m-p/4771144#M531490</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;11.31&lt;BR /&gt;&lt;BR /&gt;What is port number of nfs4cbd daemon?&lt;BR /&gt;&lt;BR /&gt;I cannot find port number via lsof -i.&lt;BR /&gt;&lt;BR /&gt;According to man nfs4cbd,&lt;BR /&gt;"nfs4cbd runs on the NFS Version 4 client&lt;BR /&gt;      and creates a listener port for each transport over which callbacks&lt;BR /&gt;      can be sent."&lt;BR /&gt;&lt;BR /&gt;Listener port should be showed.&lt;BR /&gt;&lt;BR /&gt;and how to send a callback? I'd like to test the callback.&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Mar 2011 06:24:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nfs4cbd-listener-port-number/m-p/4771144#M531490</guid>
      <dc:creator>vpar</dc:creator>
      <dc:date>2011-03-29T06:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: nfs4cbd listener port number?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nfs4cbd-listener-port-number/m-p/4771145#M531491</link>
      <description>NFS is going over RPC (remote procedure call)&lt;BR /&gt;&lt;BR /&gt;# rpcinfo -p&lt;BR /&gt;</description>
      <pubDate>Tue, 29 Mar 2011 09:37:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nfs4cbd-listener-port-number/m-p/4771145#M531491</guid>
      <dc:creator>Viktor Balogh</dc:creator>
      <dc:date>2011-03-29T09:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: nfs4cbd listener port number?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nfs4cbd-listener-port-number/m-p/4771146#M531492</link>
      <description>No nfs4cbd in output of  "rpcinfo -p"</description>
      <pubDate>Tue, 29 Mar 2011 09:53:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nfs4cbd-listener-port-number/m-p/4771146#M531492</guid>
      <dc:creator>vpar</dc:creator>
      <dc:date>2011-03-29T09:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: nfs4cbd listener port number?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nfs4cbd-listener-port-number/m-p/4771147#M531493</link>
      <description>NFS v4 typically uses a callback connection for things like file locking and delegation.  Are you using either of these?&lt;BR /&gt;&lt;BR /&gt;If you're able to lock files over NFS v4 then that's usually a good indication that the callback mechanism is working.  If you request a delegation and are granted one by the server, that's a good indication the callback mechanism is working.  You may only be able to tell the later via a network trace. &lt;BR /&gt;&lt;BR /&gt;Out of curiosity, is there a reason you're using NFS v4 over v3?  I'm interested in learning which v4 features customers use that aren't available in v3.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Wed, 30 Mar 2011 00:57:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nfs4cbd-listener-port-number/m-p/4771147#M531493</guid>
      <dc:creator>Dave Olker</dc:creator>
      <dc:date>2011-03-30T00:57:04Z</dc:date>
    </item>
  </channel>
</rss>

