Sponsored Content
Full Discussion: Environment variable
Top Forums UNIX for Dummies Questions & Answers Environment variable Post 302418002 by tirwit on Sunday 2nd of May 2010 08:05:06 AM
Old 05-02-2010
Quote:
Originally Posted by ultimatix
No that goes once u end / log out frm ur shell
So, to that variable to be defined everytime I start a new shell, I need to add the definition of the variable to .bash_profile, right?

Quote:
export TERM is for setting ur terminal size when wiorking on a console
By terminal size what do you mean? It's graphical size? Sorry for the noob questions and thanks for your help.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Environment Variable

Hello, I need some help to understand system and user environment files, such as .profile and others. I can edit my .profile file in my home directory. What I only touch in this file is the $PATH variable and when I am logged in under a telnet session, the PATH that I specify is used and... (8 Replies)
Discussion started by: jacobsa
8 Replies

2. UNIX for Advanced & Expert Users

help on environment variable

what is the environment variable used for getting the <machine name> . hello $LOGNAME,welcome to <??> I want to print the machine name in the place of <??> Please help. (6 Replies)
Discussion started by: mehuldoshi
6 Replies

3. UNIX for Dummies Questions & Answers

Environment Variable

$ . oraenv (when i type this at the prompt) ORACLE_SID = ? ( I get this) I understand that . oraenv is a startup script and it has the ENV variable ORACLE_SID. But pls let me know what more it explains and also how to change the env variable here. (2 Replies)
Discussion started by: thumsup9
2 Replies

4. Shell Programming and Scripting

Environment Variable

First of all I am using C shell. I have a variable destDirectory that holds a path. the path includes an environment variable($user) when I try to execute a command within the script, the $destDirectory gets replaced with the path, but the environment variable is not replaced. I end up... (2 Replies)
Discussion started by: karyn1617
2 Replies

5. Shell Programming and Scripting

Using Environment Variable

In our current environment we have each of our testing levels on individual servers (running Korn shell). So, there is a server for dev and test, and 2 servers for qa and prod. I have several scripts that utilize a code that is dependant on the server where it resides. While I was the only person... (3 Replies)
Discussion started by: kaiser
3 Replies

6. Shell Programming and Scripting

environment variable

Hi, I have to set bunch of variables and all other programs like make, perl will use them .. Here are my constraints and requirements ... The variables have to be set by executing a script that runs in c shell. I cannot source the script since people who use this script might be on... (8 Replies)
Discussion started by: sharanbr
8 Replies

7. Solaris

Environment variable

Hello, For the moment, my LC_ALL variable is set as "" by default. If I want to change this value, I do : export LC_ALL="en_fr" for example. That I want to know it's : how can I set by default this value ? I want to save it on my profile in order to get it when I open my session... :confused:... (2 Replies)
Discussion started by: MasterapocA
2 Replies

8. Shell Programming and Scripting

about environment variable

i am not clear at some places i saw that assigning a env var with colon ':' like export PATH=/usr/bin:/usr/ucb:/etc:/usr/sbin:.:/usr/platform/sun4u/sbin here you can find : and a . and again : could some one explain how it works... see all is starting from root directory, how : is used and... (6 Replies)
Discussion started by: Arunprasad
6 Replies

9. Solaris

Environment Variable

Hi All, I am new to SUN Solaris.I have some questions regarding environment variable.:confused: Q1. Where the environment variables available in Solaris. Q2. What command used here. Q3. Can a user change this .Suppose i want to change the bash to ksh can it be possible here. Or i need to... (2 Replies)
Discussion started by: jdash.ps
2 Replies

10. Shell Programming and Scripting

Expand an environment variable in sed, when the variable contains a slash

I'm trying to make a sed substitution where the substitution pattern is an environment variable to be expanded, but the variable contains a "slash". sed -e 's/<HOME_DIRECTORY>/'$HOME'/'This gives me the following error: sed: -e expression #1, char 21: unknown option to `s'Obviously this is... (2 Replies)
Discussion started by: Ilja
2 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 02:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy