Script Post: 302907259

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

create a shell script that calls another script and and an awk script

Hi guys I have a shell script that executes sql statemets and sends the output to a file.the script takes in parameters executes sql and sends the result to an output file. #!/bin/sh echo " $2 $3 $4 $5 $6 $7 isql -w400 -U$2 -S$5 -P$3 << xxx use $4 go print"**Changes to the table...

2. Shell Programming and Scripting

Script will keep checking running status of another script and also restart called script at night

I am using blow script :-- #!/bin/bash FIND=$(ps -elf | grep "snmp_trap.sh" | grep -v grep) #check snmp_trap.sh is running or not if then # echo "process found" exit 0; else echo "process not found" exec /home/Ketan_r /snmp_trap.sh 2>&1 & disown -h ...

3. UNIX for Dummies Questions & Answers

Calling a script from master script to get value from called script

I am trying to call a script(callingscript.sh) from a master script(masterscript.sh) to get string type value from calling script to master script. I have used scripts mentioned below. #masterscript.sh ./callingscript.sh echo $fileExist #callingscript.sh echo "The script is called"...

4. Shell Programming and Scripting

Shell script works fine as a standalone script but not as part of a bigger script

Hello all, I am facing a weird issue while executing a code below - #!/bin/bash cd /wload/baot/home/baotasa0/sandboxes_finance/ext_ukba_bde/pset sh UKBA_publish.sh UKBA 28082015 3 if then echo "Param file conversion for all the areas are completed, please check in your home directory"...

5. Shell Programming and Scripting

How to block first bash script until second bash script script launches web server/site?

I'm new to utilities like socat and netcat and I'm not clear if they will do what I need. I have a "compileDeployStartWebServer.sh" script and a "StartBrowser.sh" script that are started by emacs/elisp at the same time in two different processes. I'm using Cygwin bash on Windows 10. My...

LEARN ABOUT OSX

osacompile

OSACOMPILE(1)						    BSD General Commands Manual 					     OSACOMPILE(1)

NAME

     osacompile -- compile AppleScripts and other OSA language scripts

SYNOPSIS

     osacompile [-l language] [-e command] [-o name] [-d] [-r type:id] [-t type] [-c creator] [-x] [-s] [-u] [-a arch] [file ...]

DESCRIPTION

     osacompile compiles the given files, or standard input if none are listed, into a single output script.  Files may be plain text or other
     compiled scripts.	The options are as follows:

     -l language
	   Override the language for any plain text files.  Normally, plain text files are compiled as AppleScript.

     -e command
	   Enter one line of a script.	Script commands given via -e are prepended to the normal source, if any.  Multiple -e options may be given
	   to build up a multi-line script.  Because most scripts use characters that are special to many shell programs (e.g., AppleScript uses
	   single and double quote marks, ``('', ``)'', and ``*''), the command will have to be correctly quoted and escaped to get it past the
	   shell intact.

     -o name
	   Place the output in the file name.  If -o is not specified, the resulting script is placed in the file ``a.scpt''.  The value of -o
	   partly determines the output file format; see below.

     -x    Save the resulting script as execute-only.

     The following options are only relevant when creating a new bundled applet or droplet:

     -s    Stay-open applet.

     -u    Use startup screen.

     -a arch
	   Create the applet or droplet for the specified target architecture arch.  The allowable values are ``ppc'', ``i386'', and ``x86_64''.
	   The default is to create a universal binary.

     The following options control the packaging of the output file.  You should only need them for compatibility with classic Mac OS or for cus-
     tom file formats.

     -d    Place the resulting script in the data fork of the output file.  This is the default.

     -r type:id
	   Place the resulting script in the resource fork of the output file, in the specified resource.

     -t type
	   Set the output file type to type, where type is a four-character code.  If this option is not specified, the creator code will not be
	   set.

     -c creator
	   Set the output file creator to creator, where creator is a four-character code.  If this option is not specified, the creator code will
	   not be set.

     If no options are specified, osacompile produces a Mac OS X format script file: data fork only, with no type or creator code.

     If the -o option is specified and the file does not already exist, osacompile uses the filename extension to determine what type of file to
     create.  If the filename ends with ``.app'', it creates a bundled applet or droplet.  If the filename ends with ``.scptd'', it creates a bun-
     dled compiled script.  Otherwise, it creates a flat file with the script data placed according to the values of the -d and -r options.

EXAMPLES

     To produce a script compatible with classic Mac OS:

	   osacompile -r scpt:128 -t osas -c ToyS example.applescript

SEE ALSO

     osascript(1), osalang(1)

Mac OS X							 November 12, 2008							  Mac OS X