This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: shell-init: error retrieving current directory
- From: Andrey Repin <anrdaemon at freemail dot ru>
- To: Andy Koppe <andy dot koppe at gmail dot com>, cygwin at cygwin dot com
- Date: Fri, 16 Aug 2013 21:49:10 +0400
- Subject: Re: shell-init: error retrieving current directory
- References: <CAHWeT-b80VyH382nXA2RrNmgK1jGOrFpw_t_zpJWEv7znR7pmA at mail dot gmail dot com>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, Andy Koppe!
> This might be the same issue as a couple of previous unresolved
> reports with the same error message, but I'm not sure, so here's a new
> thread.
> Steps to reproduce:
> - On Windows 7, install 64-bit Cygwin into C:\cygwin, and let it
> create a desktop shortcut.
> - Edit /etc/fstab to change the cygdrive prefix to /.
> - Double click 'Cygwin64 Terminal' desktop shortcut.
> Result: a bunch of errors before the bash prompt.
> shell-init: error retrieving current directory: getcwd: cannot access
> parent directories: Bad file descriptor
> job-working-directory: error retrieving current directory: getcwd:
> cannot access parent directories: No such file or directory
> job-working-directory: error retrieving current directory: getcwd:
> cannot access parent directories: No such file or directory
> job-working-directory: error retrieving current directory: getcwd:
> cannot access parent directories: No such file or directory
> chdir: error retrieving current directory: getcwd: cannot access
> parent directories: No error
> The errors remain if the shortcut target is changed from invoking
> mintty to invoking bash directly: 'C:\cygwin\bin\bash.exe -l'.
> The errors go away if 'C:\cygwin\bin' is put into the shortcut's
> otherwise empty 'Start In' field. (But they stay if 'C:\' is put there
> instead.)
> They also go away if the cygdrive prefix is changed to anything but
> the root directory.
> I couldn't reproduce the issue with a 32-bit install.
Been there, done that.
http://sourceware.org/ml/cygwin/2013-06/msg00733.html
Unfortunately, the pending new VM setup was cancelled, and I've had no time to
get around to test this issue again.
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 16.08.2013, <21:44>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple