I moved my S09nfs further down the line to S20nfs and now everything is a-okay! The ctca's weren't coming fully operational at S09, but they were by S20, so that did the trick.
Thanks for the advice. Dave -----Original Message----- From: Jeremy Warren [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2003 3:55 PM To: [EMAIL PROTECTED] Subject: Re: NFS mounts in FSTAB - timing issue? Maybe the S<whatever>nfs is coming up before S<whatever>network in /etc/rc.d/rc3.d? i.e: S08nfs S10network would be bad... You might want to try moving the nfs connect to a later step too, maybe if they are back to back you might have a timing issue... ------------------------------------------- Jeremy Warren Sr. Systems Programmer KB Toy Stores 100 West St. Pittsfield, MA 01201 (413) 496-3900 mailto:[EMAIL PROTECTED] David Booher <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 08/04/2003 04:40 PM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject: [LINUX-390] NFS mounts in FSTAB - timing issue? Hello all, I'm trying to get some NFS exports to mount during IPL of my SuSE SLES 7.0 system. The following is in the fstab: suburban:/qa /qa nfs rsize=1024,wsize=1024,timeo=14,intr 0 0 suburban:/buildusr /buildusr nfs rsize=1024,wsize=1024,timeo=14,intr 0 0 When I boot, I get: <snip> Importing Net File System (NFS)mount: can't get address for suburban mount: can't get address for suburban done Starting syslog services done Starting NIS+ services: keyserv done Starting routed done </snip> It seems to me that the NFS mount is trying to take place before the network services are even capable of locating the suburban machine. Could this be the problem? If so, how do I resolve it? When the system is fully initialized, I can issue a manual mount for these and they connect-up just fine. Any help would be appreciated. Thanks!
