On 3/19/07, Craig Barratt <[EMAIL PROTECTED]> wrote:
I forgot to mention the checksum seed is sent little-endian, so the
actual bytes are "stdi". This is the first part of an error message,
like "stdin: not a tty".
The fact that this appears after the rsync protocol version is
correctly sent suggests that a backgrounded process (stty?) is
writing the characters after rsync starts.
Craig
Gentleman, Thank you for your help. This is exactly the problem. ssh -p
222 vps.deadeyedata.com /bin/sleep 10 >& test.dat test.dat still comes
out a zero-length file, but a few seconds after issuing the command I do see
the error "stdin: not a tty".
I don't use this account interactively it is strictly there for backups.
This is all that is in .bashrc in that user's profile:
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
Can I just remove those two lines to effectively prevent it from loading
.bashrc at all?
--
Charles Swarts
www.deadeyedata.com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
