Sponsored Content
Full Discussion: ksh ./sort.sh: not found
Top Forums Shell Programming and Scripting ksh ./sort.sh: not found Post 302392326 by Andre_Merzky on Thursday 4th of February 2010 04:50:46 AM
Old 02-04-2010
Question

What is the first line of your script? Could it be it does not find the interpreter?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris-ksh: directory not found

Solaris 8 using ksh: I have a directory called apps...in that directory there are some flat files and some directories. I can't access one particular subdirectory called netscape-old. I am NOT logged in as root Here is the info... user@machine>ls -l drwxr-xr-x 3 root other ... (5 Replies)
Discussion started by: dangral
5 Replies

2. UNIX for Advanced & Expert Users

ksh: cvs: not found ??

Hi, I've set up putty/ plink to work with cvs on windows and connect via ssh to unix where my cvs repository is. I want to use wincvs to log in to my cvs repository. However, I get an error when I run the following command (on windows): cvs -d :ext:user@server:/path/to/repository status ... (2 Replies)
Discussion started by: rein
2 Replies

3. Programming

ksh: make: not found

$ make ksh: make: not found Hello, when i use the "make" command in Solaris, it says the "make" command is not found! Any help appreciated! BobK (3 Replies)
Discussion started by: bobk544
3 Replies

4. Shell Programming and Scripting

procedure/function not found in .ksh

Hi all , I am getting an error "job_procfile not found" while excecuting a .ksh script. The script is used to create control-m ( scheduler ) jobs dynamically by reading parameter files ( flat filescomma seperated ) job_procfile is a function within the .ksh script The script is something... (8 Replies)
Discussion started by: rajesh_ramaoz
8 Replies

5. Shell Programming and Scripting

Problem with script: ksh not found

Hello Guys, what is the significance of using #!/bin/sh at the start of shell script. my default shell is ksh, when i run my script i have ksh: not found error and when i use ./myscript it works. Can anyone explain me the problem please ? tnx (1 Reply)
Discussion started by: midhun_u
1 Replies

6. UNIX for Dummies Questions & Answers

ksh not found in solaris

Hi , I am new to solaris world but worked in unix for a while . I have this solaris box version 8 .I am trying to run a simple unix file . Q.shl cat Q.shl #!/bin/ksh db2 get connection state When I run the file I get following error : Q.shl ksh: Q.shl: not found This is... (6 Replies)
Discussion started by: capri_drm
6 Replies

7. Shell Programming and Scripting

/bin/ksh: scriptname: not found. ???

I have started to write Korn scripts on the client's AIX 4.2 servers and there is this small problem that puzzles me. I code all my scripts the same way: - first line contains : #!/bin/ksh - I do this console command on every scripts: chmod +x scriptname But still, on some occasions,... (4 Replies)
Discussion started by: Browser_ice
4 Replies

8. Shell Programming and Scripting

ksh not found on remote server

Hi guys, I need to run batch jobs on a remote machine. I have been able to make a connection with a user2 login details via ssh, and have tested that I am in the correct directory etc. Problem is that when I try to run the batch job, I keep getting a ksh <batchjobname> not found. If doing it... (1 Reply)
Discussion started by: Hopper_no1
1 Replies

9. Shell Programming and Scripting

ksh:not found

Hi, i used to run oracle queries in unix and then transfer the result in to csv files. it was working fine for a month.but today it showed an error like ksh>dimens_minus_scpt.sh not found. Can someone please help. Thanks. :wall: (4 Replies)
Discussion started by: varadharajan87
4 Replies

10. Shell Programming and Scripting

ksh: <a perl file name> not found

I am using a perl file to run a batc job from unix prompt. I am inside the correct directory where the perl file is located. I can even find the file using ls command. But when I run the perl file , it says 'ksh: <perl_file.pl> not found'. Could anyone please let me know what is wrong? (4 Replies)
Discussion started by: Subhasis
4 Replies
console(n)						       Tk Built-In Commands							console(n)

__________________________________________________________________________________________________________________________________________________

NAME
console - Control the console on systems without a real console SYNOPSIS
console subcommand ?arg ...? _________________________________________________________________ DESCRIPTION
The console window is a replacement for a real console to allow input and output on the standard I/O channels on platforms that do not have a real console. It is implemented as a separate interpreter with the Tk toolkit loaded, and control over this interpreter is given through the console command. The behaviour of the console window is defined mainly through the contents of the console.tcl file in the Tk library. Except for TkAqua, this command is not available when Tk is loaded into a tclsh interpreter with "package require Tk", as a conventional terminal is expected to be present in that case. In TkAqua, this command is ony available when stdin is /dev/null (as is the case e.g. when the application embedding Tk is started from the Mac OS X Finder). console eval script Evaluate the script argument as a Tcl script in the console interpreter. The normal interpreter is accessed through the consolein- terp command in the console interpreter. console hide Hide the console window from view. Precisely equivalent to withdrawing the . window in the console interpreter. console show Display the console window. Precisely equivalent to deiconifying the . window in the console interpreter. console title ?string? Query or modify the title of the console window. If string is not specified, queries the title of the console window, and sets the title of the console window to string otherwise. Precisely equivalent to using the wm title command in the console interpreter. ACCESS TO THE MAIN INTERPRETER
The consoleinterp command in the console interpreter allows scripts to be evaluated in the main interpreter. It supports two subcommands: eval and record. consoleinterp eval script Evaluates script as a Tcl script at the global level in the main interpreter. consoleinterp record script Records and evaluates script as a Tcl script at the global level in the main interpreter as if script had been typed in at the con- sole. ADDITIONAL TRAP CALLS
There are several additional commands in the console interpreter that are called in response to activity in the main interpreter. These are documented here for completeness only; they form part of the internal implementation of the console and are likely to change or be mod- ified without warning. Output to the console from the main interpreter via the stdout and stderr channels is handled by invoking the tk::ConsoleOutput command in the console interpreter with two arguments. The first argument is the name of the channel being written to, and the second argument is the string being written to the channel (after encoding and end-of-line translation processing has been performed.) When the . window of the main interpreter is destroyed, the tk::ConsoleExit command in the console interpreter is called (assuming the con- sole interpreter has not already been deleted itself, that is.) DEFAULT BINDINGS
The default script creates a console window (implemented using a text widget) that has the following behaviour: [1] Pressing the tab key inserts a TAB character (as defined by the Tcl escape.) [2] Pressing the return key causes the current line (if complete by the rules of info complete) to be passed to the main interpreter for evaluation. [3] Pressing the delete key deletes the selected text (if any text is selected) or the character to the right of the cursor (if not at the end of the line.) [4] Pressing the backspace key deletes the selected text (if any text is selected) or the character to the left of the cursor (of not at the start of the line.) [5] Pressing either Control+A or the home key causes the cursor to go to the start of the line (but after the prompt, if a prompt is present on the line.) [6] Pressing either Control+E or the end key causes the cursor to go to the end of the line. [7] Pressing either Control+P or the up key causes the previous entry in the command history to be selected. [8] Pressing either Control+N or the down key causes the next entry in the command history to be selected. [9] Pressing either Control+B or the left key causes the cursor to move one character backward as long as the cursor is not at the prompt. [10] Pressing either Control+F or the right key causes the cursor to move one character forward. [11] Pressing F9 rebuilds the console window by destroying all its children and reloading the Tcl script that defined the console's be- haviour. Most other behaviour is the same as a conventional text widget except for the way that the <<Cut>> event is handled identically to the <<Copy>> event. EXAMPLE
Not all platforms have the console command, so debugging code often has the following code fragment in it so output produced by puts can be seen while during development: catch {console show} SEE ALSO
destroy(n), fconfigure(n), history(n), interp(n), puts(n), text(n), wm(n) KEYWORDS
console, interpreter, window, interactive, output channels Tk 8.4 console(n)
All times are GMT -4. The time now is 10:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy