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 environment. See the PermitUserEnvironment option in sshd_config(5).man sshd " -pekka-
Philip Nemec wrote:
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 ~/.bashrc should be called.
I reinstalled the service just in case there was something strange there (like being set to allow service to interact with desktop) - but still no luck...
So if you put some echo command in your .bashrc and then run ssh localhost pwd, you see it?
On Thu, 21 Oct 2004 20:40:26 -0400, Larry Hall <[EMAIL PROTECTED]> wrote:
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 cygwinbox pwd does *not* call ~/.bashrc...
From the bash man page:
Bash attempts to determine when it is being run by the remote shell daemon, usually rshd. If bash determines it is being run by rshd, it reads and executes commands from ~/.bashrc, if that file exists and is readable. It will not do this if invoked as sh. The --norc option may be used to inhibit this behavior, and the --rcfile option may be used to force another file to be read, but rshd does not generally invoke the shell with those options or allow them to be specified.
WFM. What's your shell in '/etc/profile'?
-- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/