https://bugzilla.novell.com/show_bug.cgi?id=856916 https://bugzilla.novell.com/show_bug.cgi?id=856916#c45 --- Comment #45 from Scott Couston <secure@aphofis.com> 2014-08-13 08:30:48 EST --- In closing I'd like to leave 2 System Logs of the last 2 boot processes and worry-some ancillary issues. They indicate what can only be felt as disturbing action via the client NFS while the PC's were left running. At not 1 time was the client NFS able to regain itself despite trying to restart NFS client services manually via Yast>Network Services>NFS client a few times during that period without success. I have the the 'soft option' as a permanent state of the NFS client's config, which, as I have described, still permits a 90 second courtesy wait time just to ensure NFS Servers do perchance become available. It is this courtesy wait period I would like changed to 10 seconds. As I have time enough not only to make a cup of coffee but its now cold when I do get access to the PC. It was this exact analogy that was used to describe booting an office full of say 10 computers under XP and extended to Vista 32bit but is somewhat moderated by its 64 bit version, irrespective of hardware performance: Microsoft was in. Now windows 8 can do a full load in less that 15 second and a recovery in under 10 and you have a serviceable accessible PC. The second system Log still shows the unknown time delay in executing phase 2 of Suse Firewall part 2 however it auto loaded NFS client services as I have changed the order in which I boot NFS Servers first then NFS clients seconds. Knowingly having to turn on PC's in a certain order just to gain short boot times in NFS clients is understandable in my test environment. Move that to an Enterprise office and you'd have to publish a procedure on what PC's to start first and in what order to actually gain access to NFS Services and/or wait the combined 120 seconds for a NFS Client and Suse-firewall part2 PC to be in a state of usability. If the NFS Servers weren’t available, the user still has a unusable PC without ANY NFS Services after 120 second and cant regain the until they re-boot their PC. In my mind having to publish an office procedure on what PC to boot first and in what order speaks to the technology of a decade ago and certainly now worthy of our enhanced O/S in the first instance. What unbelievable flexibility and sheer processing grunt we can give with our O/S we let this all fail due to both these 2 issues. Changing the NFS wait time to 10 seconds will assist dramatically, however we're better than that in being able to solve this issue far more eloquently and this is where I will leave the status of the bug for you. Please excuse my enthusiasm for knowing we have a far better O/S completely discord to NFS Services and SuseFirewall 2 loading we have on offer and this extends to our Enterprise Product but off course in this situation the Enterprise client is running a Netware File Server to permit the sharing of files etc etc and the added burden of requiring a dedicated Samba Server as well I suppose. Now is this still an eloquent solution for an Enterprise client to be in? Why not simpley fix NFS Services and permit simple file services as a adjunct to running the dedicated Samba Server in this Enterprise Mix of open and transparent file access. The questions are, off course rhetorical ones. Subsequent attachments are of the aforesaid System Logs -- 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.