View topic - rpcbind/nfsd not working with QNX6.4.1 (OK with QNX6.3.2)
rpcbind/nfsd not working with QNX6.4.1 (OK with QNX6.3.2)
6 posts
• Page 1 of 1
rpcbind/nfsd not working with QNX6.4.1 (OK with QNX6.3.2)
HI !
In sysinit file I have :
rpcbind&
nfsd&
With QNX6.3.2, at end of the script, nfsd is present in the processus list, all is fine.
With QNX6.4.1, at the end of the script, nfsd is NOT present in the list of processus. But if I launch nfsd after the script, it is OK.
I was forced to introduce a "sleep 1" between rpcbind and nfsd and then it works !!!
Any idea ?
Thank you.
In sysinit file I have :
rpcbind&
nfsd&
With QNX6.3.2, at end of the script, nfsd is present in the processus list, all is fine.
With QNX6.4.1, at the end of the script, nfsd is NOT present in the list of processus. But if I launch nfsd after the script, it is OK.
I was forced to introduce a "sleep 1" between rpcbind and nfsd and then it works !!!
Any idea ?
Thank you.
- metais
- Active Member
- Posts: 17
- Joined: Thu Mar 02, 2006 5:01 pm
RE: rpcbind/nfsd not working with QNX6.4.1 (OK with QNX6.3.2
Any ideas why you need a delay?
- maschoen
- QNX Master
- Posts: 1920
- Joined: Wed Jun 25, 2003 5:18 pm
Metais,
The nfsd probably depends on something that the rpcbind provides and in 6.4.1 rpcbind is probably a little slower to start and so nfsd fails.
You should check to see whether rpcbind registers itself in a /dev/rpcbind type manner. If it does you can replace the sleep 1 with a 'waitfor /dev/rpcbind' call
Tim
The nfsd probably depends on something that the rpcbind provides and in 6.4.1 rpcbind is probably a little slower to start and so nfsd fails.
You should check to see whether rpcbind registers itself in a /dev/rpcbind type manner. If it does you can replace the sleep 1 with a 'waitfor /dev/rpcbind' call
Tim
- Tim
- Senior Member
- Posts: 1050
- Joined: Wed Mar 10, 2004 12:28 am
Hi !
Some news :
1) /etc/rpc was missing, it is better with it (note that it is still possible to make a nfs connection without it)
2) I found nothing to wait for rpcbind (no dev/rpcbinf or something similar).
3) when removing the ampersands, nfsd no longer crash at startup (is there a rule when using ampersand ? rpcbind start in background itself ?).
thanks !
Some news :
1) /etc/rpc was missing, it is better with it (note that it is still possible to make a nfs connection without it)
2) I found nothing to wait for rpcbind (no dev/rpcbinf or something similar).
3) when removing the ampersands, nfsd no longer crash at startup (is there a rule when using ampersand ? rpcbind start in background itself ?).
thanks !
- metais
- Active Member
- Posts: 17
- Joined: Thu Mar 02, 2006 5:01 pm
This is an informative site, which have all the hottest news and updates. I have been read all the topics.
-----------------------------------
gold ring | ruby ring | emerald ring
-----------------------------------
gold ring | ruby ring | emerald ring
- bestmikal
- New Member
- Posts: 4
- Joined: Sat Mar 13, 2010 5:19 am
6 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 0 guests
