Re: Desktop freeze on NFS share failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wednesday 19 August 2015 12:20:34 Emmett Culley wrote:

> These servers are all development servers, and having NFS access allows our
> development IDE's to have direct access to the code under development.  So
> there is a very good use case for having "unstable" NFS servers on the
> network.

I don't see a functional difference between that above and a single server 
holding the code in shares (one share per dev server, for example), and both 
dev server and IDE system mounting a share. You would have to change nfs share 
to work with different code/branch, but now you changing IP of the NFS server 
anyway, so it is very similar. 

I do agree that this does not change the fact that there seem to be bigger 
issue. However changing the way you using NFS may give you working system now, 
instead of waiting for upstream to see this as an issue, which is not certain, 
and the fix it. 

Piotr
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org




[Index of Archives]     [KDE Users]     [Fedora General Discussion]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Triage]     [Coolkey]     [Yum Users]     [Yosemite Forum]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux