What kind of script hacks did you do differently from the environment
stuff mentioned by Pekka?
And although I appreciate hearing about workarounds, if this is really
a bug, let us work on actually fixing it!
On Fri, 22 Oct 2004 01:28:20 + (UTC), Christopher Cobb
<[EMAIL PROTECTED]> wrote:
>
Hi there,
I solved similar problem by enabling line
PermitUserEnvironment yes
in /etc/sshd_config and copying my .bashrc as
~/.ssh/environment
In man pages of sshd it says:
"
6. Reads the file $HOME/.ssh/environment, if it exists, and users
are allowed to change their enviro
I'm not totally sure what you're asking... My shell in /etc/passwd is
/bin/bash. Just in case I copied the /etc/defaults/profile to
/etc/profile and added a check if that even gets called.
/etc/profile *doesn't* get called with a non-interactive ssh which is
the correct behavior - only the users
Philip Nemec gmail.com> writes:
> But ssh cygwinbox pwd does *not* call ~/.bashrc...
This annoys me no end. I have had to write some quite hackish scripts to get
around this.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.
At 07:48 PM 10/21/2004, you wrote:
>As best as I can tell from the archives and man pages, ~/.bashrc
>should be called when starting an ssh session - both interactive and
>non-interactive. Tests on my Linux box behave as expected:
>
>ssh linuxbox
>ssh linuxbox pwd
>ssh cygwinbox
>
>But ssh cygwinb
As best as I can tell from the archives and man pages, ~/.bashrc
should be called when starting an ssh session - both interactive and
non-interactive. Tests on my Linux box behave as expected:
ssh linuxbox
ssh linuxbox pwd
ssh cygwinbox
But ssh cygwinbox pwd does *not* call ~/.bashrc...
>From t
6 matches
Mail list logo
