Path: utzoo!mnetor!uunet!husc6!mailrus!ames!pasteur!ucbvax!CUNIXC.COLUMBIA.EDU!cck
From: cck@CUNIXC.COLUMBIA.EDU (Charlie C. Kim)
Newsgroups: comp.protocols.appletalk
Subject: Re: Two questions about aufs
Message-ID: <8804201322.AA16542@columbia.edu>
Date: 20 Apr 88 13:22:02 GMT
References: <12391913521.156.A.ERIC@GSB-HOW.Stanford.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 22

We made a decision a while back not to support MS-DOS clients.  Even
so, Aufs doesn't deal well with AppleShare PC clients because there
are some points that errors should be returned (OpenDir, CloseDir)
when they are not (fixed in new release).  Somewhere in the mess that
I call documentation for Aufs, this is duly and dully noted.

Making Aufs work for MS-DOS clients is far from impossible, but it is
a lot more work than I can presently justify (mostly it is a matter of
handling short file names).

Creating new process for every connection isn't that much overhead
(beyond the initial fork call), but it is a decision that should be
re-evaluated at some point.  There are major advantages to running in
a single fork.  By the way, we have a MicroVax II (5MB memory, 2 RD53
driver) acting as a server for ~27 Aufs users, acting as an IP
gateway, and a lpr server.  Loads, for all they count, average around
.25-.5.  Our CPU utilization is within reasonable bounds.  Our big
problem is having enough memory to keep everything in core.  The big
thing is that people seem to be relatively happy with the performance.

Charlie C. Kim
User Services