[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ptp-dev] Fwd: Git Configuration
- From: Corey Ashford <cjashfor@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 05 Dec 2011 16:32:48 -0800
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:188.8.131.52) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16
On 12/05/2011 04:07 AM, Beth Tibbitts wrote:
> You need to make sure that a non-interactive shell gets the right
> environment setup.
> Altho, based on my expericence, .bashrc is the one it calls.
> Interactive shells can call .profile or .bash_profile (need to update
> that wiki page)
It depends on which shell you use on that remote machine. Usually the
default for Linux is set to bash, but some people like ksh, tcsh, etc.
and have their default shell set to that.
tcsh uses ~/.tcshrc, and if that doesn't exist, it tries ~/.cshrc
I've never used ksh, but looking at the man page, it appears to use the
same file as bash (and sh) - .profile
All that said, you may be asking for some obscure errors if you don't
use bash. I ran into some serious problems using TM/TCF (unrelated to
PTP!) when using tcsh on a remote machine. Switching my remote machine
to use bash instead, after debugging the plug-in to figure out what was
going wrong, fixed the problem I was having.