From: Kevin Schnitzius <kometes@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>, Andry <andry@inbox.ru>
Subject: Re: tee: 'standard output': Permission denied
Date: Wed, 30 Dec 2020 01:29:04 +0000 (UTC) [thread overview]
Message-ID: <955039478.230139.1609291744160@mail.yahoo.com> (raw)
In-Reply-To: <1626660026.20201230005056@inbox.ru>
On Tuesday, December 29, 2020, 04:47:56 PM EST, Andry via Cygwin <cygwin@cygwin.com> wrote:
> "%CYGWIN_ROOT%\bin\bash.exe" -c "{ cd ""%PWD:\=/%""; CHERE_INVOKING=. ""%CYGWIN_ROOT:\=/%/bin/bash.exe"" -l -i; } 2>&1 | ""%CYGWIN_ROOT:\=/%/bin/tee.exe"" -a ""%PROJECT_LOG_FILE:\=/%"""
```
Cannot repro... Logfile is created correctly and commands and their output are logged there. The file encoding for the logfile is utf-8.
A couple of things though: 1. changing \ to / does not guarantee a valid Cygwin path. 2. the cd does nothing because bash -l starts the shell in the home directory. 3. Once you've started bash, you don't have to supply the full path so "/bin/bash.exe" and "/bin/tee.exe" are fine (assuming your path and mounts are set correctly)
Are any files on a remote share?Are any of the paths relative?Do any of the paths have spaces in them?
You should check out the cygpath utility...
Kevin
next prev parent reply other threads:[~2020-12-30 1:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 2:04 Andry
2020-12-29 21:50 ` Andry
2020-12-30 1:29 ` Kevin Schnitzius [this message]
2020-12-30 2:22 ` Andry
2020-12-30 19:21 ` Brian Inglis
2020-12-31 16:33 ` Andry
2020-12-30 1:31 ` Doug Henderson
2020-12-30 1:45 ` Takashi Yano
2020-12-30 2:24 ` Andry
2020-12-30 4:02 ` Takashi Yano
2020-12-30 4:40 ` Takashi Yano
2020-12-30 4:54 ` Andry
2020-12-30 5:11 ` Andry
2020-12-30 4:49 ` Andry
2020-12-30 5:03 ` Takashi Yano
2020-12-30 5:18 ` Andry
2020-12-30 6:40 ` Takashi Yano
2020-12-30 10:13 ` Takashi Yano
2020-12-30 15:07 ` Andry
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=955039478.230139.1609291744160@mail.yahoo.com \
--to=kometes@yahoo.com \
--cc=andry@inbox.ru \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).