Performing new NFS mounts during Ignite installation?

[HP-UX TIM OSP]

Hello all:

I have a post install script for HP's SSH depot. I am trying to NFS mount an exported directory from the Ignite server to my client. I assume that the script is being executed on the client.

Here's a sample for the log file:
* Software installation of this source (/var/opt/ignite/pkgs/openSSH3.5)
is complete.
* Executing user specified script:
"/var/opt/ignite/scripts/configure_openSSH".
nfs mount: get_fh: 10.21.131.18:: RPC: Unknown protocol
nfs mount: get_fh: 10.21.131.18:: RPC: Unknown protocol
nfs mount: retry: retrying(1) for: /umi after 5 seconds
nfs mount: retry: giving up on: /umi
[ERROR]:Unable to NFS mount 10.21.131.18:/jumpstart/skel
to /umi
return 1
WARNING: The script: "/var/opt/ignite/scripts/configure_openSSH" returned a
warning.


I see that Ignite uses NFs mounting to get to the client LLA directory. But I have also seen in example documentation of them using rcp or tftp to get files form the buildserver. Has anybody sucessfully used NFS during an installation?

Thanks,
Nelson

[Mark Greene_1]

Most of the rpc services daemons live in /usr/sbin; however, rpcd itself is in /opt/dce/sbin/.

Are both /usr and /opt mounted at the time the script is executed?


mark