Hello all, I have a laptop on which I use a PCMCIA network card. During boot I get errors when the nfsserver is started; I think that it is because the network isn't up yet, so the nfs rpc calls fail to the file server. If I start the nfs manually, it always works. What is the best approach to fixing this? I thought about changing the order of scripts in rc3.d, but I am not sure exactly what needs to change. For example, the the pcmcia script is at S06pcmcia, while the nfs scripts are at S09nfs. Here is an excerpt from the boot.msg log: Starting external PCMCIA (using scheme: SuSE)cardmgr[218]: starting, version is 3.1.28 cardmgr[218]: modpath = /lib/modules/2.4.16-4GB/ cardmgr[218]: modsubdir = pcmcia-external cardmgr[218]: watching 2 sockets cardmgr[218]: initializing socket 1 cardmgr[218]: socket 1: 3Com 572/574 Fast Ethernet cardmgr[218]: executing: 'insmod -v /lib/modules/2.4.16-4GB//pcmcia-external/3c574_cs.o' cardmgr[218]: + Using /lib/modules/2.4.16-4GB//pcmcia-external/3c574_cs.o cardmgr[218]: + Symbol version prefix '' cardmgr[218]: executing: './network start eth0' done Starting RPC portmap daemon done Starting SSH daemon done Starting syslog services done lockdsvc: Invalid argument startproc: exit status of /usr/sbin/rpc.lockd: 1 Importing Net File System (NFS)mount: RPC: Unable to send; errno = Network is unreachable mount: RPC: Unable to send; errno = Network is unreachable done Starting service usbmgr done Starting service at daemon: done Starting cupsd done Starting identd done Thanks, Ron Cordell
participants (1)
-
Ron Cordell