Re: [BackupPC-users] Fatal error (bad version): stdin: is not a tty

[Craig B. <cba...@us...>]

Michael Brunner writes:

> I'm very new to backuppc but I solved already a lot of problems with 
> help of this mailinglist. I think I'm very close but can not fix this 
> problem. I get the following error message:
> 
> Fatal error (bad version): stdin: is not a tty
> 
> I'm using Centos and saw, that a other user also had this problem. He 
> also got an answer:
> 
>  In csh syntax this is usually done by adding something
>  like this to your .cshrc and/or .login script (prior to
>  commands like stty that are only useful for interactive
>  sessions):
>  
>      if ( ! $?USER || "$prompt" == "" || ! $?term ) then
>          exit
>      endif
> 
> 
> Unfortunately I don't know, where I should put this text, I don't have a 
> .login file and the .cshrc file doesn't contain any tty commands. I hope 
> I'm right, that I have to change this on the client computer.

Your diagnosis is correct: rsync sees the string "stdin: is not a tty",
meaning your shell startup script is running some kind of stty or
similar program when ssh tries to start rsync.  Some shells also
run a system-wide startup or login script - maybe that is running
the stty or similar program?

Craig