Sponsored Content
Full Discussion: OpenSolaris Vs. Solari8
Operating Systems Solaris OpenSolaris Vs. Solari8 Post 302309844 by surainbow on Thursday 23rd of April 2009 03:35:16 AM
Old 04-23-2009
Bug

Quote:
Originally Posted by System Shock
The error is telling you what's making the SCRIPT fail;

Code:
./complete.sh[349]: Basic_message[222]::cannot open.....

On line 349 of the script, Basic_message is being called, and complete.sh can't execute it.

I don't know what Basic_message is (another script?, a function?, environment variable? it's not an OS command, though), but whatever it is, if it is in the same directory as complete.sh or in your path, it's probably not executable.
Hi, boss
I check the SHell again, and re-run this shell, found the error occured at line 349 404 and 406, from these lines i found there is Basic_message function here...
So...i think maybe this function can not be invoked on my Opensolaris system..
can u help me check the shell again...and help me found why only these 3 line error?
if u need any infomation.....i will provide...

thanks x 100000
 

3 More Discussions You Might Find Interesting

1. Solaris

Suspend in opensolaris

How does one enable the suspend to hard drive or ram and sleep features on a desktiop running Open Solaris? (2 Replies)
Discussion started by: FloridaBSD
2 Replies

2. Solaris

Gcc for OpenSolaris

Hi All, can anyone please tell the site from where I can download gcc compiler for openSolaris..I tried to find it but unable to do it. Please help me.. (7 Replies)
Discussion started by: smartgupta
7 Replies

3. Solaris

OpenSolaris vs Solaris

What is the difference between OpenSolaris and Solaris ? Can we get the same full functionality as Solaris on SPARC in OpenSolaris ? thanks. (3 Replies)
Discussion started by: sudhiroracle
3 Replies
scotty(1)							 Tnm Tcl Extension							 scotty(1)

__________________________________________________________________________________________________________________________________________________

NAME
scotty - A Tcl shell including the Tnm extensions. SYNOPSIS
scotty ?fileName arg arg ...? _________________________________________________________________ DESCRIPTION
scotty is a Tcl interpreter with extensions to obtain status and configuration information about TCP/IP networks. After startup, scotty evaluates the commands stored in .scottyrc and .tclshrc in the home directory of the user. SCRIPT FILES
If scotty 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 scotty will read Tcl commands from the named file; scotty will exit when it reaches the end of the file. If you create a Tcl script in a file whose first line is #!/usr/local/bin/scotty2.1.11 then you can invoke the script file directly from your shell if you mark the file as executable. This assumes that scotty 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 scotty 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 scotty exec scotty2.1.11 "$0" "$@" This approach has three advantages over the approach in the previous paragraph. First, the location of the scotty 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 scotty is itself a shell script (this is done on some systems in order to handle multiple architectures or operating systems: the scotty script selects one of several binaries to run). The three lines cause both sh and scotty 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 scotty to reprocess the entire script. When scotty 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. VARIABLES
Scotty 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 scotty was invoked. tcl_interactive Contains 1 if scotty is running interactively (no fileName was specified and standard input is a terminal-like device), 0 otherwise. PROMPTS
When scotty 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 scotty 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. SEE ALSO
Tnm(n), Tcl(n) AUTHORS
Juergen Schoenwaelder <schoenw@cs.utwente.nl> Tnm scotty(1)
All times are GMT -4. The time now is 01:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy