Sponsored Content
Top Forums Shell Programming and Scripting One Script on all the Unix flavors Post 302323031 by cfajohnson on Friday 5th of June 2009 07:18:55 AM
Old 06-05-2009
Quote:
Originally Posted by tcsprak
Is it possible to have a single script that runs on all the platforms?

If you write using POSIX shell syntax, your script should run on all systems without any change and without needing to check the OS.

There are a few commands that may need changing, but they are rare.
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

UNIX flavors

Are there any flavors of UNIX which are better suited for implementation in the field of 3d animation, if so what are they? (3 Replies)
Discussion started by: aloysius1001
3 Replies

2. What is on Your Mind?

Different flavors of Linux

What are the different flavors of Linux? (1 Reply)
Discussion started by: SubbaraoV
1 Replies

3. UNIX for Dummies Questions & Answers

What exactly is a Unix Flavors means??

could anybody tell me what is a unix flavor? (4 Replies)
Discussion started by: human
4 Replies

4. Shell Programming and Scripting

FTP script for sending a file from one unix directory to another unix server director

Hi, My local server is :/usr/abcd/ Remote server is :/Usr/host/test/ I want to send files from local unix directory(All files starting with O_999) to remote host unix directory. Can any body give me the Unix Shell script to do this. One more doubt: Shall we need to change the file... (1 Reply)
Discussion started by: raja_1234
1 Replies

5. Shell Programming and Scripting

Get all types of shell supported on any unix flavors.

Hello - Is there a command/way we can find out, what shells are supported on a Unix machine? Please let me know. Thanks, Manju (3 Replies)
Discussion started by: manju--
3 Replies

6. Shell Programming and Scripting

FTP from windows to unix server using unix shell script

Hi, Is it possible to ftp a huge zip file from windows to unix server using unix shell scripting? If so what command i need to use. thanks in advance. (1 Reply)
Discussion started by: Shri123
1 Replies

7. UNIX for Dummies Questions & Answers

Unix flavors that run on x86, x86_64 bit processors?

Hello everyone. This is an awesome forum. Glad to have joined! :) I use Linux mostly, even for Desktop usage. I just love everything about it, all the way down to how the font looks while browsing. Its just so sleek and sexy. But I also boot Windows for those programs I just need that only... (23 Replies)
Discussion started by: insomnia
23 Replies

8. Shell Programming and Scripting

Time zone issues in UNIX flavors

Hello All, I am in process of migrating all my scripts from AIX box to Linux box. In one of my script I calculate my last week date with the below command $ TZ=EDT+172 date +%F 2012-12-13 $ uname -a AIX 1 7 000B29AAD400 Now when I tried running the same in Linux, it gives a false... (2 Replies)
Discussion started by: sathyaonnuix
2 Replies

9. Shell Programming and Scripting

How can i run sql queries from UNIX shell script and retrieve data into text docs of UNIX?

Please share the doc asap as very urgently required. (1 Reply)
Discussion started by: 24ajay
1 Replies

10. Shell Programming and Scripting

Downloading hdfs file to local UNIX through UNIX script

Hi All , I am very new to unix script.I am aware of unix commands but never put together in unix script level.If any one can suggest me technical guidance in the below scenario that will highly beneficial. Data have been already migrated from mainframe to Hadoop file system(HDFS).HDFS server... (15 Replies)
Discussion started by: STCET22
15 Replies
tclsh(1)							 Tcl Applications							  tclsh(1)

__________________________________________________________________________________________________________________________________________________

NAME
tclsh - Simple shell containing Tcl interpreter SYNOPSIS
tclsh ?fileName arg arg ...? _________________________________________________________________ DESCRIPTION
Tclsh is a shell-like application that reads Tcl commands from its standard input or from a file and evaluates them. If invoked with no arguments then it runs interactively, reading Tcl commands from standard input and printing command results and error messages to standard output. It runs until the exit command is invoked or until it reaches end-of-file on its standard input. If there exists a file .tclshrc (or tclshrc.tcl on the Windows platforms) in the home directory of the user, tclsh evaluates the file as a Tcl script just before reading the first command from standard input. SCRIPT FILES
If tclsh is invoked with arguments then the first argument is the name of a script file and any additional arguments are made available to the script as variables (see below). Instead of reading commands from standard input tclsh will read Tcl commands from the named file; tclsh will exit when it reaches the end of the file. There is no automatic evaluation of .tclshrc in this case, but the script file can always source it if desired. If you create a Tcl script in a file whose first line is #!/usr/local/bin/tclsh then you can invoke the script file directly from your shell if you mark the file as executable. This assumes that tclsh has been installed in the default location in /usr/local/bin; if it's installed somewhere else then you'll have to modify the above line to match. Many UNIX systems do not allow the #! line to exceed about 30 characters in length, so be sure that the tclsh executable can be accessed with a short file name. An even better approach is to start your script files with the following three lines: #!/bin/sh # the next line restarts using tclsh exec tclsh "$0" "$@" This approach has three advantages over the approach in the previous paragraph. First, the location of the tclsh binary doesn't have to be hard-wired into the script: it can be anywhere in your shell search path. Second, it gets around the 30-character file name limit in the previous approach. Third, this approach will work even if tclsh is itself a shell script (this is done on some systems in order to handle multiple architectures or operating systems: the tclsh script selects one of several binaries to run). The three lines cause both sh and tclsh to process the script, but the exec is only executed by sh. sh processes the script first; it treats the second line as a comment and executes the third line. The exec statement cause the shell to stop processing and instead to start up tclsh to reprocess the entire script. When tclsh starts up, it treats all three lines as comments, since the backslash at the end of the second line causes the third line to be treated as part of the comment on the second line. You should note that it is also common practise to install tclsh with its version number as part of the name. This has the advantage of | allowing multiple versions of Tcl to exist on the same system at once, but also the disadvantage of making it harder to write scripts that | start up uniformly across different versions of Tcl. VARIABLES
Tclsh sets the following Tcl variables: argc Contains a count of the number of arg arguments (0 if none), not including the name of the script file. argv Contains a Tcl list whose elements are the arg arguments, in order, or an empty string if there are no arg arguments. argv0 Contains fileName if it was specified. Otherwise, contains the name by which tclsh was invoked. tcl_interactive Contains 1 if tclsh is running interactively (no fileName was specified and standard input is a terminal-like device), 0 otherwise. PROMPTS
When tclsh is invoked interactively it normally prompts for each command with ``% ''. You can change the prompt by setting the variables tcl_prompt1 and tcl_prompt2. If variable tcl_prompt1 exists then it must consist of a Tcl script to output a prompt; instead of out- putting a prompt tclsh will evaluate the script in tcl_prompt1. The variable tcl_prompt2 is used in a similar way when a newline is typed but the current command isn't yet complete; if tcl_prompt2 isn't set then no prompt is output for incomplete commands. KEYWORDS
argument, interpreter, prompt, script file, shell Tcl tclsh(1)
All times are GMT -4. The time now is 12:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy