Sponsored Content
Full Discussion: OpenSolaris Vs. Solari8
Operating Systems Solaris OpenSolaris Vs. Solari8 Post 302309651 by System Shock on Wednesday 22nd of April 2009 01:11:17 PM
Old 04-22-2009
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.
 

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
SCRIPT(1)						    BSD General Commands Manual 						 SCRIPT(1)

NAME
script -- make typescript of terminal session SYNOPSIS
script [-adfpqr] [-c command] [file] DESCRIPTION
script makes a typescript of everything printed on your terminal. It is useful for students who need a hardcopy record of an interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1). If the argument file is given, script saves all dialogue in file. If no file name is given, the typescript is saved in the file typescript. Option: -a Append the output to file or typescript, retaining the prior contents. -c command Run the named command instead of the shell. Useful for capturing the output of a program that behaves differently when associated with a tty. -d When playing back a session with the -p flag, don't sleep between records when playing back a timestamped session. -f Flush output after each write. This is useful for watching the script output in real time. -p Play back a session recorded with the -r flag in real time. -q Be quiet, and don't output started and ended lines. -r Record a session with input, output, and timestamping. The script ends when the forked shell exits (a control-D to exit the Bourne shell (sh(1)), and exit, logout or control-d (if ignoreeof is not set) for the C-shell, csh(1)). Certain interactive commands, such as vi(1), create garbage in the typescript file. script works best with commands that do not manipulate the screen, the results are meant to emulate a hardcopy terminal. ENVIRONMENT
The following environment variable is used by script: SHELL If the variable SHELL exists, the shell forked by script will be that shell. If SHELL is not set, the Bourne shell is assumed. (Most shells set this variable automatically). SEE ALSO
csh(1) (for the history mechanism). HISTORY
The script command appeared in 3.0BSD. BUGS
script places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects. BSD
October 17, 2009 BSD
All times are GMT -4. The time now is 04:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy