git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Freeman <jfreeman@cs.tamu.edu>
To: Paul Johnston <pcj127@gmail.com>, git@vger.kernel.org
Subject: Re: clone fails: Could not get the current working directory
Date: Mon, 22 Sep 2008 13:32:23 -0500	[thread overview]
Message-ID: <48D7E4B7.3010109@cs.tamu.edu> (raw)
In-Reply-To: <48D6C822.7050602@cs.tamu.edu>

I have also tried copying the repo to my home directory on the remote 
Sun machine, and then cloning to my local machine.  This works as expected.

Does anyone know why a call to getcwd() would fail?

I found this in some documentation on getcwd:
http://www.opengroup.org/onlinepubs/009695399/functions/getcwd.html
"If a program is operating in a directory where some (grand)parent 
directory does not permit reading, getcwd() may fail, as in most 
implementations it must read the directory to determine the name of the 
file. This can occur if search, but not read, permission is granted in 
an intermediate directory, or if the program is placed in that directory 
by some more privileged process (for example, login). Including the 
[EACCES] error condition makes the reporting of the error consistent and 
warns the application writer that getcwd() can fail for reasons beyond 
the control of the application writer or user. Some implementations can 
avoid this occurrence (for example, by implementing getcwd() using pwd, 
where pwd is a set-user-root process), thus the error was made optional."

Does anyone know for certain if this is true for Sun machines?  Would it 
be possible to patch / introduce a macro that changes the use of 
getcwd() to a use of pwd, like the above documentation suggests?

- John

  reply	other threads:[~2008-09-22 18:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21  0:49 clone fails: Could not get the current working directory John Freeman
     [not found] ` <d3a045300809211012l35b1ec2dq39f4174170d8c926@mail.gmail.com>
2008-09-21 22:18   ` John Freeman
2008-09-22 18:32     ` John Freeman [this message]
2008-09-23 12:39 ` Alex Riesen
2008-09-23 13:23   ` John Freeman
2008-09-23 14:12     ` Alex Riesen
2008-09-23 14:45       ` John Freeman
2008-09-23 15:01         ` Alex Riesen
2008-09-23 21:16           ` John Freeman
2008-09-24 11:30             ` Alex Riesen
2008-09-24 13:30               ` John Freeman
2008-09-24 14:43                 ` Alex Riesen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48D7E4B7.3010109@cs.tamu.edu \
    --to=jfreeman@cs.tamu.edu \
    --cc=git@vger.kernel.org \
    --cc=pcj127@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).