Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199909231607.LAA23598@tigris.pounder.sol.net>
To: mlx AT san DOT rr DOT com, cygwin AT sourceware DOT cygnus DOT com
Reply-to: Tom Rodman <rodmant AT sol DOT net>
From: Tom Rodman <rodmant AT sol DOT net>
X-note: Return-Receipt-To: rodmant AT sol DOT net
Subject: Re: Vanishing mounts 
In-reply-to: Your message of "Tue, 21 Sep 1999 09:23:20 PDT."
             <9909211623 DOT AA01769 AT mlx DOT com> 
Date: Thu, 23 Sep 1999 11:07:39 -0500

We're still using bash 18 and have had a Vanishing mounts
problem; in fact we have a script/workaround whose sole
purpose is to "hold" mounts.

    #!/bin/sh
    # ***************************************************************************
    # File ....... mounts_hold_workaround
    # Author ..... rodmant
    # User ....... admin boot script
    # Synopsis ... Maintain bash mount points.
    # ***************************************************************************
    # When a non-admin user runs bash on a pc, the mounts are dropped when
    # the user exits bash.  This script works around the problem - it runs
    # at bootup and hangs around until shutdown.
    # 
    <snip>

We have not attempted to reproduce the problem under bash 20.1, NT SP4.

				     
		regards,

		Tom Rodman
   
		<tom DOT rodman AT jci DOT com>



On Tue 9/21/99 9:23 PDT mlx AT san DOT rr DOT com wrote:
>Hi all,
>
>I've been noticing for some time now that mounts seem
>to be spontaneously unmounting themselves.  There doesn't
>seem to be any rhyme or reason to when this event occurs.
>Maybe after rebooting, maybe not, etc.  I've noticed this
>ever since updating to b20.1 last January.  It happens on
>NT v4.0 sp3&sp4 and win95 boxes as well.  Both I and several
>friends who use this release have all independently noticed
>this behavior.  I guess under cygwin, this is akin to a
>registry entry spontaneously disappearing.
>
>Once again, this is the last "production" release.  I never
>mess with snapshots unless I'm experiencing serious problems
>or there is a new feature that I desire.  I had some seriously
>frustrating experiences in trying to build later snapshots with
>"_ctype" errors cropping up all over the place so I've canned
>updating (till I get a free weekend == NEVER) for "now".
>That's another thing with me & OpenSource snapshots, if I can't
>at least build it, I sure as hell ain't gonna rely on it in a
>production type environment.
>
>That's a pre-emptive answer to the old knee-jerk ->
>
>"don't question why - just upgrade to the latest snapshot"
>
>camp.
>
>Anyway, has anyone else been experiencing this problem and
>"just living with it" like us or is there some feasible explanation
>for why this is occuring ?
>
>
>Thanks in advance,
>
>Steve B.
>
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com