Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Centos 5.8 and RedHat 5.3 terminals strange behaviour Post 302622045 by Corona688 on Wednesday 11th of April 2012 12:47:50 PM
Old 04-11-2012
Your terminal emulator may be sending some sort of escape sequence to notify it that it's been resized, which the prompt wrongly accepts.
 

9 More Discussions You Might Find Interesting

1. Linux

/etc/passwd strange behaviour!

Hi there, first of all, here is my conf of a uname -a Linux SAMBA 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i686 unknown on a fedora machine. Here is my problem: every once in a while, the line containing root disappears in the /etc/passwd, disabling all logging on my server. Any one have... (0 Replies)
Discussion started by: penguin-friend
0 Replies

2. Shell Programming and Scripting

A Strange Behaviour!!!

Can some-one give me a view to this : I have a directory in an unix server, having permissions r-xr-xr-x .This directory is basically a source directory. Now there is another directory basically the destination directory which has all the permissions. Note:I log in as not the owner,but user... (5 Replies)
Discussion started by: navojit dutta
5 Replies

3. UNIX for Advanced & Expert Users

Strange sed behaviour

$ echo a.bc | sed -e "s/\|/\\|/g" |a|.|b|c| $ Is the behavior of the sed statement expected ? Or is this a bug in sed ? OS details Linux 2.6.9-55.0.0.0.2.ELsmp #1 SMP Wed May 2 14:59:56 PDT 2007 i686 i686 i386 GNU/Linux (8 Replies)
Discussion started by: vino
8 Replies

4. UNIX for Dummies Questions & Answers

Strange Program behaviour

Had a strange thing going on with my code. It's ok I figured it out for myself.... (2 Replies)
Discussion started by: mrpugster
2 Replies

5. Shell Programming and Scripting

strange behaviour from sed???

Hi all, I want to do a very simple thing with sed. I want to print out the line number of a disk I have defined in /etc/exports, so I do: It's all good, but here's the problem. When I define md0 in a variable, I get nothing from sed: Why is that? can anybody please help? Thanks (2 Replies)
Discussion started by: alirezan
2 Replies

6. Shell Programming and Scripting

Strange behaviour with perl i/o?

Hi All, I got a strange problem here. I have a perl script which is fetching data from a database table and writing a file with that data. If i run that script from linux command line, the file it creates is a normal ascii text file without any binary character in it.But... (9 Replies)
Discussion started by: DILEEP410
9 Replies

7. HP-UX

Strange login behaviour

Hi all, I am using HP-UX and I have just noticed that when I log into the network it seems to save the previous windows that were subsequently closed on previous occasions. Does anyone know when I log in, it seems to display these previous windows, e.g. nedit windows open again? Does... (1 Reply)
Discussion started by: cyberfrog
1 Replies

8. Shell Programming and Scripting

Strange RegExp Behaviour

Hello, I was trying to identify lines who has a word of the following pattern "xyyx" (where x, and ys are different characters). I was trying the following grep - egrep '(\S)()\2\1' This pattern do catches the wanted pattern, but it also catches "GGGG" or "CCCC" patterns. I was trying to... (5 Replies)
Discussion started by: itskov
5 Replies

9. Red Hat

Crontab strange behaviour

Hi all, I'm having this scenario which for the moment I cannot resolve. :( I wrote a script to make a dump/export of the oracle database. and then put this entry on crontab to be executed daily for example. The script is like below: cat /home/oracle/scripts/db_backup.sh #!/bin/ksh ... (3 Replies)
Discussion started by: enux
3 Replies
ttytype(1)						      General Commands Manual							ttytype(1)

NAME
ttytype - terminal identification program SYNOPSIS
type] DESCRIPTION
automatically identifies the current terminal type by sending an identification request sequence to the terminal. This method works for local, modem, and remote terminal connections, as well as for the and terminal emulators. Once the terminal has been identified, prints the terminal's type to the standard output (see terminfo(4)). This string is usually used as the value for the environment variable. If is unable to determine the correct terminal type, it prompts the user for the correct terminal identification string. Options recognizes the following options: Causes to return an ID of "unknown" instead of prompting for the terminal type if auto-identification fails. If this option is not present, interactively prompts the user for the terminal type if it is unable to determine the correct type automati- cally. Causes to prompt for the terminal type before it sends the terminal identification request sequence. If the user responds with only a carriage return, proceeds with the automatic terminal identification process. Any other response is taken as the correct terminal type. Note that the and variables are not set if the user manually enters a terminal type. The option is normally used only for terminals that do not behave well when presented with terminal identification request sequence. It gives the user a chance to respond with the correct terminal type before any escape sequences are sent that could have an adverse effect on the terminal. The option can be used in conjunction with the option. The option only inhibits interactive prompting after has failed to identify the terminal by other means. Tells to print a series of shell commands to set the and environment variables to appropriate values. In addition, the variable is set to the two-character sequence representing the appropriate erase character for the terminal (DEL for ANSI termi- nals, backspace for all others). This two-character sequence can then be used as an argument to or (see stty(1) and tset(1)). The environment variable is consulted to see which shell syntax to use for setting the environment variables. This output is normally used with a command of the form: normally attempts identification of Wyse, ANSI and HP terminals. The type argument can be used to restrict the inquiry to that required for terminals of the specified type. The accepted types are and Multiple options can be specified. Enable verbose messages to standard error. Notes Use of the option is highly recommended because many terminals support variable-size displays. This option provides the only means for automatically configuring the user environment in such a manner that applications can handle these terminals correctly. Note that and are not set if the option is used and the user manually enters a terminal type. The following steps are performed in the order indicated when identifying a terminal: 1. tries the Wyse 30/50/60 id request sequence. 2. tries the standard ANSI ID request sequence. If a response is received, it is converted to a string according to an internal table. 3. tries the HP id request sequence. 4. If none of the above steps succeed, prompts interactively for the correct terminal type unless the option has been given. may skip one or more of the first three steps, depending on the presence of options. The HP ID request sequence can switch some ANSI terminals into an unexpected operating mode. Recovery from such a condition sometimes requires cycling power on the terminal. To avoid this problem, always sends the HP identification sequence last. EXAMPLES
is most commonly used as part of the login sequence. The following shell script fragment can be used during login shell initialization: # # If TERM is not set, see if our port is listed in /etc/ttytype. # If /etc/ttytype doesn't have information for our port, run # ttytype(1) to try to determine the type of terminal we have. # # To have ttytype(1) prompt for the terminal type before trying # to automatically identify the terminal, add the "-p" option # to the "ttytype -s" command below. # if [ -z "$TERM" -o "$TERM" = network ]; then unset TERM eval `tset -s -Q` if [ -z "$TERM" -o "$TERM" = unknown ]; then eval `ttytype -s` tset -Q -e ${ERASE:-^h} $TERM fi fi WARNINGS
The terminal identification sequences sent by can cause unexpected behavior on terminals other than the Wyse 30/50/60, standard ANSI or HP terminals. If you have such terminals in your configuration, use the or options to prevent from sending sequences that cause unexpected behavior. AUTHOR
was developed by HP. SEE ALSO
csh(1), ksh(1), sh(1), stty(1), ttytype(4), environ(5). ttytype(1)
All times are GMT -4. The time now is 06:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy