Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20041021203449.04ec5bb8@pop.prospeed.net> X-Sender: Date: Thu, 21 Oct 2004 20:40:26 -0400 To: Philip Nemec , cygwin AT cygwin DOT com From: Larry Hall Subject: Re: .bashrc not called for non-interactive ssh sessions In-Reply-To: <4d211735041021164839ba2ac3@mail.gmail.com> References: <4d211735041021164839ba2ac3 AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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/