On Thu, Jul 18, 2002 at 10:02:40PM -0500, Scott G. Akmentins-Taylor wrote: > > Since the latest update to OpenSSH there is a small thing that has > > appeared on my machines (STABLE as of 30 Jun) When I run scp from a box > > (it can be of any brand of OpenSSH) I get two lines saying: > > > > tput: tgetent failure: No such file or directory > > tput: tgetent failure: No such file or directory > > > > The copy goes fine, but what does this mean? > > Hi. > > The errors are a result of something in your .profile or .cshrc > that is trying to modify the stdout as a tty device. > stty is the usual cause of this. Your particular error messages > indicate that some program being executed at the remote shell's > startup of .profile or .cshrc (or via them) is trying to perform > a tgetent() call upon the stdin or stdout, but since those won't > be a tty(4) type path, the calls fail. > > Check your .profile or .cshrc and ensure that you're not attempting > to modify the stdin/out via stty(1). If you have such code in there, > use conditionals to only perform them when an interactive login is > detected.
Thanks! The tput thing came from a central bashrc, I installed a couple of weeks ago. I'll remove the stty thing in it. > > I hope this helps. > > -scott > -- > Scott G. Akmentins-Taylor InterNet: [EMAIL PROTECTED] > Cray Inc, Minneapolis, MN - USA [EMAIL PROTECTED] > SV2/UNICOS Distribution Engineering > ----- Labak miris neka sarkans - Vienoti Latvijai! ----- -- Gunnar Flygt, Postmaster SR To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
