02-02-2010
Quote:
Originally Posted by
FrankToy
@xanthos
Did the path display okay ? The space at the end of the lines was there in my script but not in the post so my guess is that it isn't okay.
Yes I,ve got the two backslash at the beginning,
You can try with #!/bin/bash
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have couple of shell scripts.
Each shell script accepts command line argument as inputfilename.
Each shell script creates a summary file, status file.
All these files are stored in a particular directory...Eg
InputFile is to be picked from /home/ProjectName/ftp_inputfiles/
Outputs are to... (1 Reply)
Discussion started by: Amruta Pitkar
1 Replies
2. Shell Programming and Scripting
Hi,
I have a file paths.txt with all the file paths. I want to tar everything in those paths to a file.
for example paths.txt contains
/data/extention
/logs/extension
/code/extenstion
Now I want to tar using command
tar cvf extention.tar path1 path2
where
path1 -> /data/extention... (2 Replies)
Discussion started by: muaz
2 Replies
3. Shell Programming and Scripting
There is a file paths.txt with paths containing data for example
E:/<BUILD_NAME>/data/common
E:/<BUILD_NAME>/log/common
E:/<BUILD_NAME>/temp/common
E:/<BUILD_NAME>/code/common
While reading this file I want to replace the <BUILD_NAME> from a variable $BUILD in the following command:
tar... (1 Reply)
Discussion started by: muaz
1 Replies
4. Shell Programming and Scripting
Hi everyone! I'm pretty bad at shell scripting and I am trying to create a java launcher. The idea is to store in a configuration file different paths (each for a different java version) and then, run a .sh file that would read the specified java path and execute the .jar file. This is what i have... (7 Replies)
Discussion started by: mostacholoco
7 Replies
5. UNIX for Dummies Questions & Answers
Hi!
I would like to funnel a series of directories and subdirectories into a text file. This is the output I would like to see from a find command:
/mypath/ABC_01/VISIT_01
/mypath/ABC_01/VISIT_02
/mypath/ABC_01/VISIT_03
/mypath/ABC_02/VISIT_01
/mypath/ABC_03/VISIT_01
I've tried:
find... (2 Replies)
Discussion started by: goodbenito
2 Replies
6. Shell Programming and Scripting
Hi guys,
I'm working on a large set of scripts to move files around several servers and manipulate them for our staff. Basically we're shooting things, the videos hit a server and then need organised due to the language they've been shot in. Our XML (designed for Apple's Final Cut Pro) is right... (6 Replies)
Discussion started by: omfgbunnies
6 Replies
7. Shell Programming and Scripting
Hello all,
I am new to scripting and here is what I want to get done.
I need to run some processing on many files. I have a whole bunch of files among which there are a few that I am interested in. What I need to do is to write a script which reads the file paths from a text file. line by... (1 Reply)
Discussion started by: pavo-cristatus
1 Replies
8. OS X (Apple)
Hi all my very first post so go easy on me!!
I am trying to build a very simple script to list a file path with spaces in. But I can't get around this problem. My script is as follows:
#!/bin/bash
X="/Library/Users/Application\ Support/"
LS="ls"
AL="-al"
$LS $AL $X
The response I... (5 Replies)
Discussion started by: tillett22
5 Replies
9. Shell Programming and Scripting
I am working on a script for Mac OS X that, among many other things, gets a list of all the installed Applications. I am pulling the list from the system_profiler command and formatting it using grep and awk. The problem is that I want to be able to use each result individually later in the script.... (3 Replies)
Discussion started by: cranfordio
3 Replies
10. Shell Programming and Scripting
Hi I want to know how to handle the spaces in the below scenario.
I have a file (CON_zip_path_1.txt) which has some directory paths with spaces in directory names . My requirement is to unzip these zip files to
another path. Please see the code below and the error.
CON_zip_path_1.txt... (4 Replies)
Discussion started by: paul1234
4 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)