| 1 |
On 5/27/06, John Jolet <john@×××××.net> wrote: |
| 2 |
> |
| 3 |
> > |
| 4 |
> > That was the hint I needed. It's /bin/bash, which reminded me I |
| 5 |
> > just changed something |
| 6 |
> > in .bashrc which outputs a message and does some other stuff which |
| 7 |
> > must be |
| 8 |
> > confusing scp. In fact, I just confirmed that by commenting it |
| 9 |
> > out. Now scp works too. |
| 10 |
> > So: PROBLEM SOLVED. |
| 11 |
> > |
| 12 |
> > Now I just have to figure out how to tailor it some more so the |
| 13 |
> > offending code is skipped |
| 14 |
> > for 'scp'. That I can do. |
| 15 |
> > |
| 16 |
> |
| 17 |
> bash has a built-in variable that tells you what the command |
| 18 |
> was....should be able to test for "scp" in your script.... i've |
| 19 |
> never tried to get that fancy with .bashrc. |
| 20 |
> -- |
| 21 |
> gentoo-user@g.o mailing list |
| 22 |
> |
| 23 |
> That does not work for ssh/scp sessions. I usually test $PS1 to tell |
| 24 |
if it's really a shell -- the variable does not even exist for an scp |
| 25 |
session, |
| 26 |
although .bashrc gets called. |
| 27 |
|
| 28 |
++ kevin |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Kevin O'Gorman, PhD |
Archives