06-24-2014
Thank you Scott, your code worked without any modification. I'm still new to scripting.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all, I have major errors on entering the shell. On login I get:
-bash: dircolors: command not found
-bash: tr: command not found
-bash: fgrep: command not found
-bash: grep: command not found
-bash: grep: command not found
-bash: id: command not found
-bash: #
root@host # pwd
/bin... (0 Replies)
Discussion started by: wcmmlynn
0 Replies
2. UNIX for Dummies Questions & Answers
Hi all, dummy here.... I have major errors on entering the shell. On login I get:
-bash: dircolors: command not found
-bash: tr: command not found
-bash: fgrep: command not found
-bash: grep: command not found
-bash: grep: command not found
-bash: id: command not found
-bash: [: =: unary... (12 Replies)
Discussion started by: wcmmlynn
12 Replies
3. Shell Programming and Scripting
Hi,
For my bash script, terminal with bash is generate an OK output and program works right.
already,
terminal with ash have "line 48: syntax error: Bad substitution" output and program don't work.
:confused: (0 Replies)
Discussion started by: s. murat
0 Replies
4. Shell Programming and Scripting
Hello everyone,
I got this type of error when programming in bash
new.bat: 16: cannot create : Directory nonexistent
$bool
new.bat: 37: Syntax error: "then" unexpected (expecting "fi")
Does anyone know why?
Here is my code
#!bin/bash
#function helps(){... (4 Replies)
Discussion started by: bbbash
4 Replies
5. UNIX for Dummies Questions & Answers
Guys
I now have a script that's working in a BASH environment, however one line doesn't appear to be working on an embedded device that has a busybox therefore ASH shell. I've googled but there's very little I can find regarding the ASH shell.
In BASH the following line works...
if ] ;... (6 Replies)
Discussion started by: Bashingaway
6 Replies
6. Shell Programming and Scripting
I'm working on a script that will search through a directory for MKV files and remux them to MP4. I found a few other scripts around the net that do this, but they all have limitations that don't always get the job done. The main limitation I've found is that most scripts look for the video track... (2 Replies)
Discussion started by: rayne127
2 Replies
7. Shell Programming and Scripting
Hi All,
I have a script that I wrote on a bash shell, I use it to sort files from a directory into various other directories. I have an variable set, which is an array of strings, I then check each file against the array and if it is in there the script sorts it into the correct folder.
But... (5 Replies)
Discussion started by: sgtbobie
5 Replies
8. Ubuntu
I'm trying to convert this working bash script into an Ash script,
read -p "Username:" _username
if ! ]]; then
echo "Valid"
else
echo "INVALID"
fi
However, Ash does not recognize the "=~" character.
How can I do this?
Also, is there a good reference guide, so I... (5 Replies)
Discussion started by: fzivkovi
5 Replies
9. Ubuntu
hello everybody,
i'm a beginner in ash and i want to convert this bash script to ash.
this script send a xml file to a nagios server :
#!/bin/bash
PROGNAME=$(basename $0)
RELEASE="Revision 0.3"
print_release() {
echo "$RELEASE"
}
print_usage() {
echo ""
echo "$PROGNAME... (6 Replies)
Discussion started by: mdijoux25
6 Replies
SDP(1) BSD General Commands Manual SDP(1)
NAME
sdp -- scripting definition (sdef) processor
SYNOPSIS
sdp -f {ahst} [-o directory | file | -] [options...] [file]
DESCRIPTION
sdp transforms a scripting definition (``sdef'') file, or standard input if none is specified, into a variety of other formats for use with a
scriptable application. The options are as follows:
-f format
Specify the output format. The format may be one or more of the following. Use these when you want to create a scriptable applica-
tion:
a Rez(1) input describing an 'aete' resource.
s Cocoa Scripting ``.scriptSuite'' file.
t Cocoa Scripting ``.scriptTerminology'' file.
These formats are only necessary when creating a scriptable application that will run on Mac OS X 10.4 (Tiger) or earlier; as of 10.5
(Leopard), an application may use only an sdef.
Use these when you want to control a scriptable application:
h Scripting Bridge Objective-C header.
You do not need to create a corresponding implementation file; Scripting Bridge will create the class implementations at runtime.
-i includefile
Include the type and class definitions from the specified sdef. It may be repeated to specify multiple files. This option is obso-
lete; you should use an XInclude element in the sdef instead.
-o directory | file | -
Specify where to write the output. There are three styles:
directory Write the output to automatically named files in that directory. Depending on the input and formats, sdp may generate
several files.
file Write all the output to that file.
- Write all the output to standard output.
The default is '-o .'; i.e., generate files in the current directory. Because Cocoa Scripting requires each suite to be in a separate
file, using -o file with -f s or -f t is usually not a good idea.
Some output formats have additional options relevant only to that format. For scriptSuite and scriptTerminology files (-f s and -f t):
-V version
Specify the minimum system version to be compatible with, for example, ``-V -10.4''. The default is to assume the current system ver-
sion. Specifying anything before 10.3 will use NSString for 'file' type attributes, and will warn about non-object direct parameters.
For Scripting Bridge Objective-C header files (-f h):
--basename name, -N name
Specify the ``base'' name. This name becomes the base name of the generated header and the prefix attached to all the generated
classes. For example, saying --basename iTunes would result in a header file ``iTunes.h'' defining a iTunesApplication class.
--hidden, -A
Output definitions even for items the scripting definition marks as hidden. All such definitions will be flagged as deprecated, since
hidden items are usually hidden for a reason.
SEE ALSO
sdef(5)
BUGS
sdp's error reporting leaves much to be desired. It does not provide line numbers for errors, though it will describe the element. It will
not warn you of certain types of mistakes, such as using two different names with the same code (or vice versa), and will return a zero sta-
tus even for erroneous input.
Mac OS X July 12, 2007 Mac OS X