https://bugzilla.novell.com/show_bug.cgi?id=819515
https://bugzilla.novell.com/show_bug.cgi?id=819515#c1
Scott Couston
From there another service starts which invokes the kernel handling of NFS drives.
My comment about putting this issue to bed forever, with respect to my comment about moving all NFS Services to the kernel was based on the following thoughts. It is helpful to me and I hope yourself if I use the example of Novell Netware. The Netware (kernel) for want of a better term will continue to try to connect back to any network drive that is either present or no present. In the same thoughts, why cant we leave the entire job of NFS drives to the kernel and NO other service running outside of it. At the moment they way 12.2 handles NFS drives after LSB: fails to start the kernel is invoked somewhere to perform...(I have no Idea) All I know is that NFS Services now both server and client, all up to 5 minutes and will wait until a huge timeout parameter is met before the boot process goes any further. I think, in solving this issue we also need to add the smarts that IF an NFS service cannot be started due its opposition client/server not being found; the kernel will continue to try and mount the NFS mount point and when the PC comes online, the NFS is auto mounted without any user intervention. Somewhat like Netware's shell retryes to reconnect any network drive, device or complete the NDS structure on a dynamic basis. The other thought I had is why dont we have all NFS Services advertise continually and this is when a lost NFS mount is dynamically connected. Sometime when the client PC cannot find its server and both PC's come online later, the NFS should auto dynamically load due to us making changes to advertised services becoming available without the user doing everything Jiri, We got to fix this for Enterprise builds. This is such a fundamental flaw that just watching the boot process bot stall and knowing when its opposite devices comes online; no auto connect or reconnect takes place. Anyway mate, let me know what logs you require from me to help and I have NO idea how this issue escapes the day to day of Suse v X and NFS continues to fail; without any developer realises the problem themselves??? Let me know how I can help Scott -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.