Hi Brett, On Sat, Aug 14, 2010 at 5:19 AM, Brett Haydon <br...@haydon.id.au> wrote:
> Wouldn't it be more efficient to use the --noprofile option by default or > perhaps have it as an env, sudo, run option? Thus far I've been operating on the principle that the average user is going to expect the remote end to "behave" in a similar fashion to an interactive SSH session to the same box, w/r/t $PATH and other exported vars -- thus the use of the -l flag (which is what forces a login shell and thus sources .bashrc, .bash_profile etc). And since env.shell is user-editable (as you found out) that provides a quick and easy way for "power users" to disable the sourcing of login files when that presents problems for them. > BTW I did try using env.shell=False but quite a few of my functions failed so > gave that idea away. Yea, turning the shell off entirely is typically less desirable -- it's best to remove the "-l" instead (which would prevent sourcing of either bashrc OR profile files). Depending on your intent you might actually want to do that instead of adding the "--noprofile". Best, Jeff > > cheers, > > Brett > > > _______________________________________________ > Fab-user mailing list > Fab-user@nongnu.org > http://lists.nongnu.org/mailman/listinfo/fab-user > -- Jeff Forcier Unix sysadmin; Python/Ruby developer http://bitprophet.org _______________________________________________ Fab-user mailing list Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user
