Sponsored Content
Full Discussion: having ksh script problems
Top Forums UNIX for Dummies Questions & Answers having ksh script problems Post 7227 by LivinFree on Friday 21st of September 2001 03:21:41 AM
Old 09-21-2001
Yeah, you've got it.
It will loop as long as it's not told to exit. The tput command, and the clear command in that statement only do a cleanup - the tput rmso returns your terminal to normal, as opposed to reverse coloring, and clear, well - it clears the screen Smilie

I think you're on the right track though - I think it might be a good idea to copy and paste this script and execute it to see how it works...

Try putting the command "set -x" at the top of the script to see what's happening, and try changing it around a little to see what changes have what effect...
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Problems with Perl/KSH Web Log Script

Hi, I am writing a series of scripts for work to analyse intranet access logs. All of the scripts do as they should when run individually from the shell, but only when run from certain directories. This sounds like it may be a PATH issue but I am not sure. When I run a certain script, say... (3 Replies)
Discussion started by: mmanders
3 Replies

2. Shell Programming and Scripting

executing a ksh script from another ksh script

Hi, I'm new to unix scripting.How can i call a script from another script. I have a.ksh and b.ksh .I have to call b.ksh from a.ksh after it is successfully exceuted. I tried using #!/bin/ksh -x in a.ksh and at the end i have used /path/b.ksh My problem is it is executing only a.ksh.it... (6 Replies)
Discussion started by: ammu
6 Replies

3. Shell Programming and Scripting

tracing a ksh script within a ksh script

I normally trace a script with the ksh -x <script name> and redirect strderr to file. But if you have a script like the examble below...... vi hairy bear=`grep bear animals` if then ksh more_animals fi If I ksh -x hairy it won't trace "more_animals" unless I put a -x in it. Is... (1 Reply)
Discussion started by: shorty
1 Replies

4. Shell Programming and Scripting

Strange parameter passing problems (KSH)

Hi all, I'm having a rather peculiar problem involving parameter passing with declared functions in my shell script. Hope to get some advice here. A brief description of my code is as follows: However, I'm not getting the results I wanted. If I pass in $rdir, I'm going to end up... (4 Replies)
Discussion started by: rockysfr
4 Replies

5. Shell Programming and Scripting

import var and function from ksh script to another ksh script

Ih all, i have multiples ksh scripts for crontab's unix jobs they all have same variables declarations and some similar functions i would have a only single script file to declare my variables, like: var1= "aaa" var2= "bbb" var3= "ccc" ... function ab { ...} function bc { ... }... (2 Replies)
Discussion started by: wolfhurt
2 Replies

6. Shell Programming and Scripting

autosys/ksh - problems with script

Hi, I'm using autosys and want to set it up that I receive emails when certain jobs start and finish. I don't want to edit each jobs script (ksh) to send a mail at start and finish, I would rather have a single script/job that watches for a trigger when the jobs have started or finished. I... (1 Reply)
Discussion started by: weszardoz
1 Replies

7. Shell Programming and Scripting

KSH script to run other ksh scripts and output it to a file and/or email

Hi I am new to this Scripting process and would like to know How can i write a ksh script that will call other ksh scripts and write the output to a file and/or email. For example ------- Script ABC ------- a.ksh b.ksh c.ksh I need to call all three scripts execute them and... (2 Replies)
Discussion started by: pacifican
2 Replies

8. Solaris

Problems Running KSH on Solaris 10

Hi, I am currently in the process of testing upgrading from Solaris 8 to Solaris 10. one problem i have encountered is when i am running any of my batch scripts. All my scripts start with #! /bin/ksh so that they will excuted in the ksh shell. but the scripts will not run correctly. The... (3 Replies)
Discussion started by: dshakey
3 Replies

9. Shell Programming and Scripting

Problems with ksh

I have the following ksh code and I am passing f="npt06-sr40-syn-dc0p02-32x24drw.mis" For some reason, it's going to the else statement instead of setting optfdrw=1 smptag=$(print -R $f | awk '/smp/') drwtag=$(print -R $f | awk '/drw/') if && ; then # drw tag... (15 Replies)
Discussion started by: kristinu
15 Replies

10. Shell Programming and Scripting

problems with ksh array and find command

set -A allfiles `find $usrhtml -type f` i am trying to populate this array with the find command. It works fine when find is looking through a single directory but when i add a new subdirectory the files in the subdirectory get duplicated. Can anyone help me and fix this so each files in... (1 Reply)
Discussion started by: bjhum33
1 Replies
tput(1) 							   User Commands							   tput(1)

NAME
tput - initialize a terminal or query terminfo database SYNOPSIS
tput [-T type] capname [parm...] tput -S << DESCRIPTION
The tput utility uses the terminfo database to make the values of terminal-dependent capabilities and information available to the shell (see sh(1)); to clear, initialize or reset the terminal; or to return the long name of the requested terminal type. tput outputs a string if the capability attribute (capname) is of type string, or an integer if the attribute is of type integer. If the attribute is of type boolean, tput simply sets the exit status (0 for TRUE if the terminal has the capability, 1 for FALSE if it does not), and produces no out- put. Before using a value returned on standard output, the user should test the exit status ($?, see sh(1)) to be sure it is 0. See the EXIT STATUS section. OPTIONS
The following options are supported: -Ttype Indicates the type of terminal. Normally this option is unnecessary, because the default is taken from the environment variable TERM. If -T is specified, then the shell variables LINES and COLUMNS and the layer size will not be referenced. -S Allows more than one capability per invocation of tput. The capabilities must be passed to tput from the standard input instead of from the command line (see the example in the EXAMPLES section). Only one capname is allowed per line. The -S option changes the meaning of the 0 and 1 boolean and string exit statuses (see the EXAMPLES section). OPERANDS
The following operands are supported: capname Indicates the capability attribute from the terminfo database. See terminfo(4) for a complete list of capabilities and the capname associated with each. The following strings will be supported as operands by the implementation in the "C" locale: clear Display the clear-screen sequence. init If the terminfo database is present and an entry for the user's terminal exists (see -Ttype, above), the following will occur: 1. if present, the terminal's initialization strings will be output (is1, is2, is3, if, iprog), 2. any delays (for instance, newline) specified in the entry will be set in the tty driver, 3. tabs expansion will be turned on or off according to the specification in the entry, and 4. if tabs are not expanded, standard tabs will be set (every 8 spaces). If an entry does not contain the information needed for any of the four above activities, that activity will silently be skipped. reset Instead of putting out initialization strings, the terminal's reset strings will be output if present (rs1, rs2, rs3, rf). If the reset strings are not present, but initialization strings are, the initialization strings will be output. Otherwise, reset acts identically to init. longname If the terminfo database is present and an entry for the user's terminal exists (see -Ttype above), then the long name of the terminal will be put out. The long name is the last name in the first line of the ter- minal's description in the terminfo database (see term(5)). parm If the attribute is a string that takes parameters, the argument parm will be instantiated into the string. An all numeric argument will be passed to the attribute as a number. EXAMPLES
Example 1: Initializing the terminal according to TERM This example initializes the terminal according to the type of terminal in the environment variable TERM. This command should be included in everyone's .profile after the environment variable TERM has been exported, as illustrated on the profile(4) manual page. example% tput init Example 2: Resetting a terminal This example resets an AT&T 5620 terminal, overriding the type of terminal in the environment variable TERM: example% tput -T5620 reset Example 3: Moving the cursor The following example sends the sequence to move the cursor to row 0, column 0 (the upper left corner of the screen, usually known as the "home" cursor position). example% tput cup 0 0 This next example sends the sequence to move the cursor to row 23, column 4. example% tput cup 23 4 Example 4: Echoing the clear-screen sequence This example echos the clear-screen sequence for the current terminal. example% tput clear Example 5: Printing the number of columns This command prints the number of columns for the current terminal. example% tput cols The following command prints the number of columns for the 450 terminal. example% tput -T450 cols Example 6: Setting shell variables This example sets the shell variables bold, to begin stand-out mode sequence, and offbold, to end standout mode sequence, for the current terminal. This might be followed by a prompt: echo "${bold}Please type in your name: ${offbold}c" example% bold='tput smso' example% offbold='tput rmso' Example 7: Setting the exit status This example sets the exit status to indicate if the current terminal is a hardcopy terminal. example% tput hc Example 8: Printing the long name from terminfo This command prints the long name from the terminfo database for the type of terminal specified in the environment variable TERM. example% tput longname Example 9: Processing several capabilities with one invocation This example shows tput processing several capabilities in one invocation. This example clears the screen, moves the cursor to position 10, 10 and turns on bold (extra bright) mode. The list is terminated by an exclamation mark (!) on a line by itself. example% tput -S <<! > clear > cup 10 10 > bold > ! ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of tput: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. TERM Determine the terminal type. If this variable is unset or null, and if the -T option is not specified, an unspecified default ter- minal type will be used. EXIT STATUS
The following exit values are returned: 0 o If capname is of type boolean and -S is not specified, indicates TRUE. o If capname is of type string and -S is not specified, indicates capname is defined for this terminal type. o If capname is of type boolean or string and -S is specified, indicates that all lines were successful. o capname is of type integer. o The requested string was written successfully. 1 o If capname is of type boolean and -S is not specified, indicates FALSE. o If capname is of type string and -S is not specified, indicates that capname is not defined for this terminal type. 2 Usage error. 3 No information is available about the specified terminal type. 4 The specified operand is invalid. >4 An error occurred. -1 capname is a numeric variable that is not specified in the terminfo database. For instance, tput -T450 lines and tput -T2621 xmc. FILES
/usr/include/curses.h curses(3CURSES) header /usr/include/term.h terminfo header /usr/lib/tabset/* Tab settings for some terminals, in a format appropriate to be output to the terminal (escape sequences that set margins and tabs). For more information, see the "Tabs and Initialization" section of terminfo(4) /usr/share/lib/terminfo/?/* compiled terminal description database ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
clear(1), sh(1), stty(1), tabs(1), curses(3CURSES), profile(4), terminfo(4), attributes(5), environ(5), standards(5), term(5) SunOS 5.10 1 Feb 1995 tput(1)
All times are GMT -4. The time now is 09:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy