I had to do the above to make it work. Why the Hadoop code can't gracefully accept a failure for this one call, I don't understand. If access fails, the code should give a 'permission denied' error. Calling chmod should just be a silent helper, not a deal-killer.
On Fri, Nov 18, 2011 at 12:59 AM, Sean Owen <[email protected]> wrote: > Oh I think you're right, looking at the Hadoop source. It is using chmod, > not a Java API. > Yes I understand how chmod and cygwin work. cygwin intercepts all path > resolution logic in the OS and rewrites it. > It may well be an issue with finding the chmod command in the end, but, I > think it ought to work in theory; it's on the "OS" path, and the OS can > translate paths correctly. Or else, this would never work. > > On Fri, Nov 18, 2011 at 3:12 AM, Lance Norskog <[email protected]> wrote: > > > 'chmod' is the program that sets readable permission. It does whatever > > Windows magic is required to match the Posix command line semantics. > > The cygwin path is not the true windows path. So, when Java runs it gets > > the true path which has no Cygwin. > > > > You have to add c:\cygwin\bin to the windows path variables. This happens > > in Computer->Properties->Advanced System Settings-> Environment > Variables. > > > > Now, for those of you snickering- I am about to hose down my Mac with > Linux > > because the key mappings make macos unusable, and I'm leaving my Windows > > laptop alone. > > > > > -- Lance Norskog [email protected]
