Home / server / Questions

Questions[xterm](server)

Martin Hope
Lito
Asked: 2011-08-25 03:55:46 +0800 CST
  • 12

I have a problem executing a cron process to check current CPU use in my server.

My script start with:

top -c -n 1 -u www-data > /tmp/kill-cpu

I can execute without problem in console, but in cron I get

top: failed tty get

If I use the -b option to top

top -b -n 1

I get

'dumb': unknown terminal type.

I'm using xterm as TERM

Thanks for your help :)
Lito.

SOLUTION: I was able to solve the problem with:

ln -s /lib/terminfo/d/dumb /usr/share/terminfo/d/dumb
cron top term xterm
Martin Hope
Mark Freeman
Asked: 2011-06-11 10:36:15 +0800 CST
  • 2

We have an old C program which has traditionally been run from SCO boxes. We have a customer that went with RackSpace running RHEL and we got the app recompiled. We have a problem with terminal emulation though. We've been trying PuTTY over SSH, but we can't seem to get the emulation settings right so that we can use the keyboard, arrow keys, and numeric keypad. We've tried SCO, linux, Xterm, VT100+. If we use ansi_sysk, the number pad works, but arrow keys don't. If we use xterm, the arrow keys work, but number pad doesn't.

Anyone have suggestions?

emulation terminal xterm
Martin Hope
thornomad
Asked: 2010-03-25 14:24:22 +0800 CST
  • 44

Just learned about the screen command on linux - it is genius. I love it. However, the actual terminal/prompt in screen looks and behaves differently than my standard bash prompt. That is, the colors aren't the same, tab completion doesn't seem to work, etc.

Is there a way I can tell screen to behave just like a normal (at least, normal as in what I am used to) bash prompt ?

Additional Information

I am connecting via ssh from a Mac (Terminal) to a headless linux box (Ubuntu). After logging in, I have TERM=xterm-color and when I run screen I have TERM=screen.

Am going to try the suggestions below to see if I can change the $TERM value first.

bash gnu-screen xterm
Martin Hope
Steve Madsen
Asked: 2010-03-16 07:34:16 +0800 CST
  • 14

I have a problem that crops up when using Mac OS X's Terminal (TERM=xterm): sometimes it gets itself into a state where lines that scroll off the top are not added to the scrollback buffer. I'm not using screen or similar; this is a plain bash shell inside a Terminal tab.

It doesn't do this immediately after opening a new tab. I believe it is a side-effect of something I've run in the problem tab. My guess is that it has something to do with the xterm emulation, possibly the scroll region.

What hasn't worked:

  • Soft and hard reset via the Shell menu
  • Running reset in the tab

Is there a reliable way to reset Terminal and/or the xterm state?

Can anyone provide a explanation for what's happening, even if the only fix is to close the tab and open a new one?

shell terminal xterm
Martin Hope
skrostislav
Asked: 2010-02-06 11:05:39 +0800 CST
  • 5

I have just installed the latest stable version of FreeBSD to a computer and I have the following problem:

If, in Putty, I issue a command like ps uxa which gives long lines of output, they get cropped. ps uxa|more doesn't help. Even if I do ps uxa > file.txt, lines are cropped to 80 chars in the file!

There are some images of how it looks like: http://yfrog.com/0rfilecroppx

This happens right after clean installation, with everything set to default. Default shell is csh, changing it to bash didn't help. This has never happened to me in Linux.

My uname -a

FreeBSD freebsd.localdomain 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009
[email protected]:/usr/obj/usr/src/sys/GENERIC  i386

How to fix this problem? I have already looked at env vars, .profile, .cshrc, /etc/login.conf.

bash freebsd putty xterm