Ray Daoud writes:
: On Sat, 6 May 2000, Sami Lehtinen wrote:
:
: > Do the user's shell scripts output something to stdout? This
: > would mess with the filexfer-protocol.
: >
: > (for example,"echo foobar" in .cshrc would do something like this.)
:
: Yes, we have also narrowed this problem down on our site to the "set
: prompt" command in users .cshrc files.
:
: I've been trying out all different sorts of fixes but, there are
: simply too many variations of shells/config files to do this easily.
:
: It seems to me it would be much cleaner (and easier ;-)) to modify
: the servers behavior to ignore .cshrc when subsystem-sftp is
: executed. Can you recommend a way to do this (or are we even allowed
: to do this?)? Is SSH working on a fix for this problem?
Aargh, I *hate* this kind of kludges.
sh, bash and zsh (I presume ksh also behaves like this) don't source
their rc-files, if they are non-interactive (ie. executing command).
tcsh (atleast, and very probably csh (I can't verify this right this
minute)) source their rc-files even if non-interactive. If they are
given the argument "-f", they won't read the dot-rc files at startup.
Suggestions? Should I check if the shell is "*csh" and give the
argument "-f", if executing a command?
--
[[EMAIL PROTECTED] -- Sami J. Lehtinen -- [EMAIL PROTECTED]]
[work:+358 9 85657425][gsm:+358 50 5170 258][http://www.iki.fi/~sjl]
[SSH Communications Security Ltd. http://www.ssh.com/]
