* coda, or alternative?
@ 2003-03-05 13:51 urgrue
0 siblings, 0 replies; only message in thread
From: urgrue @ 2003-03-05 13:51 UTC (permalink / raw)
To: linux-admin
i have two servers connected via gigabit ethernet. the one on the "far
end" is basically a backup server from which i've mounted a few drives,
to which the near-end server writes directly. the line is very reliable
but it does have its problems once in a while.
NFS is awful, absolutely AWFUL, when there's a connection problem. it
can end up hanging the whole machine (because many processes/scripts
try to write to the mounted drive, and they all hang, eventually
gumming up the whole system).
but i'd really like it mounted, as the amount of data that needs to be
transferred is a bit loo large to let collect up on the near-end
server. it doesnt matter if all attempts to write to the mount totally
fail when the line is down, just so long as the machine survives nicely.
so i'm looking at coda, but everywhere i see warnings like "barely read
for production use", "experimental", "development", etc....
samba has been good to me in other situations, but i'm a bit reluctant
to use it because it doesnt behave all that nicely either (needs manual
remounting often, etc. plus, linux pride counts ;)
is coda good enough despite these warnings, or are there other
alternatives?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-03-05 13:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-03-05 13:51 coda, or alternative? urgrue
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).