How can I avoid running .bashrc?

How can I avoid running .bashrc when I specify a command to be executed
*AND* use the -t option because the command needs tty semantics?

What I'd really prefer is to directly execute the command WITHOUT running
it through the shell at all. I know that would mean either something else
has to parse the command string into tokens, or the command has to be
provided already broken into tokens. But I guess that means extending
the SSH protocol so it can transfer the command as separated tokens instead
of a single string.

But for some reason, using -t triggers running the shell in interactive
mode as opposed to command mode. Is ssh/sshd doing that or is the shell
detecting this and making an assumption?

If there was at least some environment variable set going into the shell
that would indicate a command is being provided on the command line, then
I could at least code the .bashrc to skip everything if that environment
variable is set. But I did some tests and see nothing distinctive between
these cases.

--
|---------------------------------------/----------------------------------|
| Phil Howard KA9WGN (ka9wgn.ham.org) / Do not send to the address below |
| first name lower case at ipal.net / spamtrap-2008-03-08-2016@xxxxxxxx |
|------------------------------------/-------------------------------------|
.

Relevant Pages

  • Re: Redirection issue
    ... 1- execute input commands from standard input, ... the phrase "it does not work anymore" carries very little meaning. ... after compilation and execution of the shell with a simple command like ... all the command in the file are executed as well. ...
    (comp.lang.c)
  • Re: Redirection issue
    ... 1- execute input commands from standard input, ... the phrase "it does not work anymore" carries very little meaning. ... after compilation and execution of the shell with a simple command like ... all the command in the file are executed as well. ...
    (comp.lang.c)
  • Re: shell scripting
    ... and am assuming an sh-compatible shell here.... ... command 1 options arguments ... To run the script, do: ... then you need to use the full path to execute it: ...
    (comp.unix.questions)
  • Re: shell scripting
    ... and am assuming an sh-compatible shell here.... ... command 1 options arguments ... To run the script, do: ... then you need to use the full path to execute it: ...
    (comp.unix.shell)
  • Why newbies dont RTFM...
    ... Even though I've used Linux before, I've never had to do any ... BASH BUILTIN COMMANDS ... last command exited within ... unless the shell is not exeâ ...
    (comp.os.linux.misc)