Sponsored Content
Full Discussion: What Happened :(
Top Forums UNIX for Dummies Questions & Answers What Happened :( Post 302189190 by jazz8146 on Friday 25th of April 2008 07:44:11 AM
Old 04-25-2008
Ha Ha
Silly me it was a typo!
The script is for files with extensions so when i was testing it yesterday i was using

q.1 q.2 q.3

not

q1 q2 q3 which has no file extensions so would not work with my script lol
 

8 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

what happened?

A few hours ago I made several reasonable posts to this forum and now they have dissapeared. I read and followed the rules, and I sure didn't break any, but gone they are :( I know I only joined the forum today, but do the posts have to be authorised or something? ... (14 Replies)
Discussion started by: cw1972
14 Replies

2. UNIX for Dummies Questions & Answers

What happened to my user accounts?

Ahhhh!!!!!!!! All of my user accounts can no longer login. I suspected a corrupt passwd file, but everything looks OK and the passwd file works when I copy it to another system. All user accounts cannot login...they recieve a "No directory defined" error, but I can logon using root just fine. I... (13 Replies)
Discussion started by: jskillet
13 Replies

3. SuSE

What happened to my three threads?

I posted three specific queries relating to Suse earlier today but they've disappeared. I originally incorrectly posted them in the Unix begiiners forum, edited them out from there and re-posted under Linux. I'm guessing they've been mistaken for some kind of flood post as they have the same... (3 Replies)
Discussion started by: Mark Ward
3 Replies

4. What is on Your Mind?

what happened to ygor..??

:D anyone hear from ygor..? haven't seen him post in a while... wonder what he is up to..! the last i heard he was the D25khan.. that was him right guys ??? being a newbie myself that is one dude that i admire. him Norsk, Perdebro, RTM , Google and Zazzybob all real genius.. and the most... (2 Replies)
Discussion started by: moxxx68
2 Replies

5. Shell Programming and Scripting

What happened with AWK?

The second script seems not to work. (3 Replies)
Discussion started by: endeavour1985
3 Replies

6. UNIX for Dummies Questions & Answers

What happened to mkisofs ?

I've been using a mkisofs line like this for years without problem # mkisofs -J -R -V 'Vol Label' -o /output/path/FILE.ISO /input/path/ Now, however, it gives a UTR-8 character message at the start INFO: UTF-8 character encoding detected by locale settings. Assuming UTF-8... (0 Replies)
Discussion started by: Bobby
0 Replies

7. Solaris

what happened to admintool?

what happened to admintool in Solaris10? (2 Replies)
Discussion started by: mndavies
2 Replies

8. What is on Your Mind?

What happened to coolerbooks?

I just found the website coolerbooks.com a couple weeks ago. It was a site that had loads of free ebooks for download. But now it seems to have been hijacked by some Microsoft search thing. There was an article last year claiming it teamed with Google (the anti-Microsoft!) to offer the... (2 Replies)
Discussion started by: KenJackson
2 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 02:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy