Sponsored Content
Full Discussion: showmount
Operating Systems Solaris showmount Post 302303587 by amult on Friday 3rd of April 2009 03:32:54 AM
Old 04-03-2009
This is what it shows:

nfs dfshares:server: RPC: Rpcbind failure - RPC: Unable to receive
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

showmount

SIZE=3]Is the only root can "showmount". How to set a user to be able "showmount"? (1 Reply)
Discussion started by: mcaelbukch
1 Replies

2. Solaris

showmount -e : solaris 10

Hi Admins; I am working on nfs mount on solaris10. I can mount the remote directory from remote nfs server, but when I try "showmount -e serverIP " on client ; it shows nothing, just hanging... Anyone does know why showmount is not showing the exported share? Thanks (2 Replies)
Discussion started by: snchaudhari2
2 Replies

3. AIX

Showmount don't show NFS4

Configure nfs4 on aix ok i did all chnfsdom #return correct domain chnfs -r /export chnfs -p /export configured and shared pseudo root #etc/exports /export -nfsroot /var/pubblica -exname=/export/pubblica,vers=4,sec=sys:krb5p:krb5i:krb5:dh,rw exportfs -a mount correct mount... (1 Reply)
Discussion started by: Linusolaradm1
1 Replies
RpcHdr(3I)						    InterViews Reference Manual 						RpcHdr(3I)

NAME
RpcHdr - header for remote procedure calls SYNOPSIS
#include <Dispatch/rpchdr.h> DESCRIPTION
An RpcHdr enables an RPC request to be sent or received. To send an RPC request, you would insert an RpcHdr into an rpcstream followed by any arguments and then flush the rpcstream if you wanted the request to be sent immediately. The rpcstream automatically fills in each RPC request's length field. To receive an RPC request, you would extract an RpcHdr from an rpcstream and examine the ``request()'' member to determine which additional arguments need to be extracted as well. You can examine the ``ndata()'' member too if you need to estimate how much space to allocate. CONSTRUCTORS
RpcHdr(void* writer, int request) RpcHdr(int request) RpcHdr() Construct an initialized header for an outgoing RPC request (first two constructors) or construct an uninitialized header for an incoming RPC request (third constructor). To initialize the header, you'll have to store the request's protocol number. You can also store the address of the writer sending the RPC request if you want to route the RPC request to a specific reader on the peer's side. PUBLIC OPERATIONS
unsigned long reader() int request() unsigned int ndata() Get information about the RPC request. ``reader()'' identifies the reader which should handle the RPC request. ``request()'' iden- tifies the action that should be performed. ``ndata()'' gives the number of data bytes following the header, which may be useful for estimating the amount of space that must be allocated to store an argument. SEE ALSO
RpcReader(3I), RpcWriter(3I), rpcstream(3I) InterViews 27 March 1991 RpcHdr(3I)
All times are GMT -4. The time now is 07:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy