RE: NFS mount for TQM823L

I send you in attach the 'rpc' and 'services' files I loaded
on the target (I hand-wrote them first, unsuccessfully:
I copied then these ones from the host).

This is a good approach. The files seem to be correct.
(BTW, I think the rpc file comes with the glibc distribution).

(Note that I type the 'mountd' command, but it doesn't
appear in the ps -aux output list!)

I guess it died, even after successfully registered with the portmapper.
Here are some ideas I have to verify everything.

1) Does it produce a core file?

2) You may start mountd with the following options:
     mountd --debug all --foreground
   This will start mountd in foregroud, turning on debugging information.
   I hope it will help...

3) You may also start the syslog daemon, to be sure you don't miss important
information.

4) Also, is the file /etc/exports present?

5) I see that the nfs startup script performs a 'exportfs -r' before
starting the daemons.
   Could it help?

While if I type the same command for the host the
mountd uses a different port number...

This is correct, since the port number is assigned randomly, unless you use
the command line option '-p' to force mountd to bind to a specific port. The
rpc port number should be identical, and correspond to what is in /etc/rpc.

while, exactly meantime, the following message appears
on the target's console:

svc: unknown program 100005 (me 100021)

The mountd process (rpc port 100005) is not in the process table, because it
unexpectedly died, even if the registration still appears in the portmap...
as if you kill mountd with a SIGKILL (9) :-(

Good luck!
--------------------------------------------
 Jean-Denis Boyer, B.Eng., Technical Leader
 Mediatrix Telecom Inc.
 4229 Garlock Street
 Sherbrooke (Québec)
 J1L 2C8  CANADA
 (819)829-8749 x241
--------------------------------------------

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

3) You may also start the syslog daemon, to be sure you don't miss

important

information.

Dear Jean-Denis,
this above has been the key suggestion that lead me to success!!!
Finally we could remote-mount our target's file system
under whatever host (not every one, really) in our local network!
Without the syslogd daemon I couldn't have been able to
discover that the 'etab' file was missing in /var/lib/nfs target's
directory.
I don't know the rule or the meaning of all the lines and keywords
that are in this file: I would like to know ,  in addition to the
capability to make them run...
Who does create this file, on the hosts for example?
 Which command or daemon?
I add here another pair of question, that would complete the
scene.

1) Does it produce a core file?

What do you mean with 'core file'?

2) You may start mountd with the following options:
   mountd --debug all --foreground
  This will start mountd in foregroud, turning on debugging information.
   I hope it will help...

How should I have debugged then? (I couldn't do it)
I have seen nothing: should any message have appeared?

At last I want to thank you very much for your precious help, and
I hope that our correspondence could help somebody else.

Best regards

Piero Dominioni
R.S.R. srl


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/