Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 17 Sep 2004 17:20:39 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: Problem with cat under bash shell
In-Reply-To: <414B1FEC.5010302@yahoo.co.uk>
Message-ID: <Pine.GSO.4.61.0409171718390.15615@slinky.cs.nyu.edu>
References: <NUTMEGbDt3HvoFOAmEa0000001c AT NUTMEG DOT CAM DOT ARTIMI DOT COM> <414B1FEC DOT 5010302 AT yahoo DOT co DOT uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: MIMEDefang 2.39

On Fri, 17 Sep 2004, Lionel Barnett wrote:

> Dave Korn wrote:
>
> >   The fact that mounting your /tmp on a remote drive is a pretty rare thing
> > would be another reason.  Remote home dirs, yes, remote /bin dirs yes,
> > remote /tmp...... not so commonly done.  Owing to a) there's generally no
> > need nor use for sharing the contents of /tmp with other users and b) it
> > gets used pretty heavily and mostly for temporary files and data that are
> > going to be needed again imminently, so for efficiency purposes it would be
> > nice if the data didn't have to make a round-trip across the network to a
> > server and then back again when it could just stay on your local machine
> > where it's needed in the first place.
>
> Agreed - things are actually noticeably zippier with a local /tmp
> (particularly as our network is somewhat crapulous).
>
> As to how/why we ended up with a remote /tmp is as follows: our work setup is
> that most of our (shared) software - including Cygwin - sits on a shared drive
> on machine S, say. We generally terminal serve in to machines A, B, C, ...
> over the network and run stuff from there (which may access fs's on machines
> X, Y, Z...). Now since the default Cygwin install sets up /tmp as... well,
> /tmp, under our setup this means /tmp sits on machine S which will be remote
> as far as machines A, B, C are concerned. I wouldn't have thought this to be
> such an uncommon setup.
>
> Hence the solution to symlink /tmp to /cygdrive/c/temp, as this is guaranteed
> to be local. Perhaps this could get a mention in the FAQ/Install notes?

It's actually better to re-mount /tmp as a local dir instead, e.g.

mount -fsb c:/temp /tmp

That way you avoid one network access for each /tmp access (to read the
symlink).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing."  -- Dr. Jubal Harshaw

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/