X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: occasional problem: .bash_profile permission denied
Date: Thu, 20 Sep 2007 10:56:54 +0200
Message-ID: <387E9FC1619C0849BA8934938037E54F12AD4F@sv-muc-004.venyon-mail.local>
From: "Ronald Fischer" <ronald DOT fischer AT venyon DOT com>
To: <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l8K8v7P2019020

I configured my system so that it automatically starts Cygwin
during boot time via the Windows autostart feature, by using
startxwin and Cygwin/X to start several xterm and rxvt terminals,
and also to start one bash shell in plain Cygwin (outside X).

Occasionally, one or two of the shells started that way complain

  bash: /cygdrive/h/.bash_profile: Permission denied

Of course there is nothing wrong with my .bash_profile, and if I
then do a manual

  . .bash_profile

in these shells, everything works manually.

It is certainly not a X specific issue, because it had occured already
in the plain Cygwin shell too.

My first idea was that perhaps that it could be a race condition between
Windows starting the Autostart applications and mounting the network
drives,
because my $HOME is on a network drive. But this would not explain the 
following: When I start several xterm's from my startxwin.bat, it
happens
sometimes that the "permission denied" error occurs on one of the
terminals
started *later*, while the earlier started ones don't have this problem.

Any idea what could be wrong here?

Ronald
-- 
Ronald Fischer <ronald DOT fischer AT venyon DOT com>
Phone: +49-89-452133-162

--
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/