Re: Network File serving options

From: Justin Robbs (justin_robbsNO_at_SPAMhotmail.com)
Date: 10/30/03 

Date: Thu, 30 Oct 2003 15:33:30 -0700

> Given your description, I'd have to say Yes.. NFS is the way to go.
>
> Nothing else would be as invisible to the client machines, requiring much
> more customization.
>
> NFS should be very stable, so long as the server it's self is. I've not
> had any issues with NFS under OSR505 or 506.
>
> bkx

Thanks for the advice. That is about what I figured based on my limited
experience.

Justin

Relevant Pages

  • V210 BGE0@1000FDX (Adam Tomkinson)
    ... sunmanagers Digest, Vol 31, Issue 28 ... When connecting a server to a Gig interface you need to enable autoneg ... Blocked port after process kill ... NFS oddity ...
    (SunManagers)
  • V210 BGE0@1000FDX
    ... When connecting a server to a Gig interface you need to enable autoneg ... Blocked port after process kill ... NFS oddity ... where hostname is the name of the NFS client which will automount the ...
    (SunManagers)
  • Solved: Perl/NFS "Text File Busy" Error And Related Problems
    ... Â That means I am actually editing the Perl file on ... and I am running it on another (my server). ... The first problem I had was that when I saved my script through NFS, ... apt-get install nfs-kernel-server ...
    (Debian-User)
  • RC1 dump hangs - sometimes
    ... nfs send error 35 for server backup:/back ... K8-class CPU) ... port may not be enabled ...
    (freebsd-current)
  • 7.0 RC1 dump hangs - sometimes
    ... nfs send error 35 for server backup:/back ... K8-class CPU) ... port may not be enabled ...
    (freebsd-current)