This is the mail archive of the
mailing list for the Cygwin project.
.bashrc not called for non-interactive ssh sessions
- From: Philip Nemec <pnemec at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 21 Oct 2004 16:48:25 -0700
- Subject: .bashrc not called for non-interactive ssh sessions
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=aYPnaN6Y4QM0JxGwu0CfFbiWTVzqRLqBl9owBnwZsFzjz3sDkzh6qD5Tfvx07MVCO0sGttazGfWQBGxyh2ZPSoBKlpQ6O9f3mL3fKDAdayYF7yrKq5FN1IbYD6utPLOZEUGwszcod2r2EBM+mzlidECWxldv4v3+jUoYI3UvjA0=
- Reply-to: Philip Nemec <pnemec at gmail dot com>
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 pwd
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.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html