🚀 go-pugleaf

Peter T. Breuer wrote:
> In comp.os.linux.networking Oliver Hookins <ohook000@nospam.student.mq.edu.au> wrote:
> 
>>Peter T. Breuer wrote:
>>
>>Sorry. That was the output from the server only. On the client, I use ps 
> 
> 
> I don't understand what you mean. I don't know anything about a server
> or a client from your description. I only know that you have a machine
> on which statd won't run. The above output shows a machine on which
> statd is running. Correct your experimental procedure.

I mentioned there was a server and a client in the first post. From 
other posts I've read in various places I thought it might be a 
pertinent point to mention the setup I am using.

In any case here is the output from ps which (I believe) shows portmap 
is running:

   PID  Uid     Stat Command
     1 root     S    [swapper]
     2 root     S    [kflushd]
     3 root     S    [kupdate]
     4 root     S    [kswapd]
     5 root     S    [keventd]
     6 root     S    init
    49 root     S    /sbin/syslogd -m 0
    55 root     S    /usr/bin/tail -f /proc/kmsg
    56 root     S    /usr/bin/tail -f /var/log/messages
    57 root     S    -sh
    58 root     S    /sbin/dbootstrap
    65 root     S    [rpciod]
    91 daemon   S    sbin/portmap
    95 root     R    ps

> So what!  Why are you telling me?  You should be running rpcinfo as I
> asked you to!  I really don't feel like playing games of 20 questions to
> screw information out of you! Show the rpcinfo output and we will know.

Sorry; if I knew where the problem lies then I'd know exactly what 
information to provide. Thanks for being patient. Here is the output 
from 'rpcinfo -p', which obviously shows something is wrong:

rpcinfo: can't contact portmapper: RPC: Remote system error - No buffer 
space available

Incidentally if I run rpc.statd in the foreground (i.e. not as a 
daemon), it exits with the following error:

Cannot register service: RPC: Unable to send; errno = No buffer space 
available

Regards,
Oliver.