From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sshd default user PATH
Date: Tue, 19 Aug 2014 11:22:00 -0000 [thread overview]
Message-ID: <20140819112229.GA24235@calimero.vinschen.de> (raw)
In-Reply-To: <20140819105829.GO2280@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Aug 19 12:58, Corinna Vinschen wrote:
> On Aug 19 09:08, Achim Gratz wrote:
> > Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> > > That means the patch to sshd isn't that important. Nevertheless, I
> > > just released cygrunsrv-1.60-1, which prepends /bin to $PATH.
> > >
> > > Funny enough, the README file claimed that /bin gets prepended to $PATH
> > > since the early days. Just the actual code didn't follow suit :-P
> >
> > The help output from the command still talks about adding it to PATH, so
> > that may actually have been intentional: prepending /bin might mess up
> > things if someone actually wants to get something in front. All things
> > considered, I suggest that cygrunsrv doesn't fiddle with the PATH if an
> > explicit PATH environment has been given on the command line, ...
>
> Sounds like a good idea to me.
Or, for backward compatibility reasons, better append /bin if PATH is
given explicitely via -e.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-08-19 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 9:57 Achim Gratz
2014-08-14 11:20 ` Corinna Vinschen
2014-08-14 12:17 ` Corinna Vinschen
2014-08-14 12:50 ` Andrey Repin
2014-08-14 12:28 ` Achim Gratz
2014-08-14 13:01 ` Achim Gratz
2014-08-14 15:19 ` Corinna Vinschen
2014-08-19 9:08 ` Achim Gratz
2014-08-19 10:58 ` Corinna Vinschen
2014-08-19 11:22 ` Corinna Vinschen [this message]
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=20140819112229.GA24235@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).