ttytype equivalent command in Solaris.


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting ttytype equivalent command in Solaris.
# 1  
Old 06-11-2009
ttytype equivalent command in Solaris.

Hi All,

We are trying to migrate scripts from HP Unix to Solaris server, in one of the profile file following command is used to set terminal settings and export its value,

"ttytype -a -s "

Now the same command is not present in Solaris, could someone let me know which command should i use, I know we can use stty to set the TERMS, LINES, COLUMNS, and ERASE env manually. But in case of 'ttytype' it dertermines the TERM automatically (like TERM = vt100) and then exports it.

Any help on this matter, please let me know if any confusions.

Thanks,
Arvind.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

solaris sed equivalent

Hi Experts, I am using this command to edit the file contents and also add the header to the existing file. I prepared this command on my VM (Linux) and it worked as I wanted it to work. But on solaris its not working :(. Please help as it is quite urgent. sample File: a b Output... (5 Replies)
Discussion started by: sugarcane
5 Replies

2. AIX

smitty equivalent command line command

i know after you do something in smitty via the gui, you can click something in smitty that will show you how to do the same thing via the command line, (not using the gui) can anyone tell me how (2 Replies)
Discussion started by: asyed123
2 Replies

3. Solaris

ignite hp-ux, which is the equivalent in solaris?

functions... ---------- Post updated at 02:51 PM ---------- Previous update was at 02:22 PM ---------- sorry i didnīt put the header in the message. i use to add this to cron in hp-ux for do the ignite 00 00 1,15 * * /opt/ignite/bin/make_net_recovery -s <IGNITE SERVER> -n 1 -P s -u -x... (5 Replies)
Discussion started by: pabloli150
5 Replies

4. UNIX for Dummies Questions & Answers

Equivalent of /etc/rc.local in Solaris 10

What is the equivalent of /etc/rc.local in Solaris 10? (4 Replies)
Discussion started by: proactiveaditya
4 Replies

5. Solaris

need solaris /etc/default/fs equivalent file in redhat Linux

contents of /etc/default/fs file in solaris are @:/root !ksh less /etc/default/fs LOCAL=ufs i want to retrieve same LOCAL variable in redhat Linux... any1 knows path of corresponding file in Linux? (3 Replies)
Discussion started by: crackthehit007
3 Replies

6. Solaris

solaris equivalent to the linux screen command

hi there is there a solaris equivalent to the linux screen command? (1 Reply)
Discussion started by: milhan
1 Replies

7. UNIX for Dummies Questions & Answers

What is the equivalent of Solaris snoop in Linux

What is the equivalent of Solaris snoop in Linux I could not find snoop in RHEL (2 Replies)
Discussion started by: santosh149
2 Replies

8. Shell Programming and Scripting

ps ax equivalent in solaris

I am using "ps ax" command in one of my scripts . AIX has x flag for ps . is there any equilent command for ps ax in solaris ? Thanks (1 Reply)
Discussion started by: talashil
1 Replies

9. Solaris

I want a command in solaris equivalent to glance in HP-UX

Hi, C an someone help me out in getting the command to get system statistics like CPU, DISK and I/O utilization in a single command instead of mpstat,vmstat and iostat. When i give sar, getting the following error, bash-3.00# sar sar: can't open /var/adm/sa/sa15 No such... (6 Replies)
Discussion started by: grrajeish
6 Replies

10. Solaris

Solaris equivalent of the ioscan command

What is the Solaris equivalent of the HP-UX "ioscan -funC" command which lists all hardware on the system? (5 Replies)
Discussion started by: etc
5 Replies
Login or Register to Ask a Question
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)