On Sat, 14 Apr 2001, Nate Amsden wrote: > Joe 'Zonker' Brockmeier wrote: > > > > On Sat, 14 Apr 2001, Nate Amsden wrote: > > > > > this only happens on 1 machine..(i run a couple dozen potato > > > servers/workstations), when trying to scp to or from it i get this: > > > > > > [EMAIL PROTECTED]:~$ scp [EMAIL PROTECTED]:/home/aphro/window.xwd . > > > [EMAIL PROTECTED]'s password: > > > Linux xxx.xxx.xxx 2.2.18 #1 Fri Jan 26 15:45:53 PST 2001 i686 unknown > > > [EMAIL PROTECTED]:~$ Write failed flushing stdout buffer. > > > write stdout: Broken pipe > > > > > *snip* > > > > According to the OpenSSH FAQ, if you have a .bashrc or .profile > > that produces output for non-interactive sessions it can confuse > > scp. That's just a guess, though. > > > > I've seen the same thing happen once or twice - but oddly enough > > it's something that hasn't be reproducible for me. It might happen > > once in 200 or 300 times that I've used scp to move files about > > from computer to computer on my local network. > > > > You can find the FAQ here: > > > > http://www.openssh.com/faq.html#2.8 > > > > If that's not actually the problem, or if it is, let us know. > > I'd be interested to know what solves it. > > > > Oh, you might also look and see if it's logging some errors. > > It's possible that you'll find the answer there. > > that was it! i removed my .bashrc and .bash_profile and its working now :) > > thanks a lot!!
That's great! Glad it helped. Take care, Zonker -- Joe 'Zonker' Brockmeier [EMAIL PROTECTED] ICQ: 43599611 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "Liberty's too precious a thing to be buried in books... Men should hold it up in front of them every single day of their lives and say: I'm free to think and to speak. My ancestors couldn't, I can, and my children will. Boys ought to grow up remembering that." "Mr. Smith Goes to Washington" -- James Stewart
