Hi Scott...Thanks a lot for ur help..but you know I am in a fix again
Code:
nohup ./processProv.sh &
while true
do
count=`ps -ef | grep processProv | wc -l`
if [ $count -gt 1 ]
echo "Process is running (Process Prov)
er=`grep -i Error processProv.log | wc -l` #a log where I need to check error generated or not parallely along with this#
if [ $er -ge 2 ]
echo "Error found "
exit 1
fi
fi
sleep 5
done
.....but it is getting stuck after the main process (nohup ./processProv.sh &) is getting complete(maybe because of sleep 5 command)...can you please suggest an alternate code so that the : process running + error check is also validated as long as the main script runs?...processProv.log is the log which gets creates once ./processProv.sh starts...
Last edited by Scott; 08-23-2013 at 11:41 AM..
Reason: Please use code tags
I'm puzzled by this one. I hope you can explain it to me.
I have a ksh shell script that gzips a file among other things. This works perfectly fine when the script is manually run through a shell. However, when the same script is run through cron, it does everything correctly, but it will... (2 Replies)
Hi all,
I have two ksh scripts
#sample1.sh
#!/bin/ksh
. ./sample2.sh
echo $fileExist
#sample2.sh
#!/bin/ksh
func()
{
i=1
return $a
}
func
echo $?
Here how should I return the value of sample2.sh back to sample1.sh?
Thanks in advance. (2 Replies)
Please help me on below..
https://www.unix.com/shell-programming-scripting/141533-retrieve-value-environment-variable-shell-script-called-crontab.html#post302442024
I'm still here. I can still see you! (0 Replies)
There are two files one is shell script (sample.sh) and another is configuration file (sampl_conf.cfg)
configuration file contains one variable $FTP_HOME. the value of this variable vaires for user to user. If user is say jadoo then value is /home/jadoo/ftp/, for user1 - /home/user1/ftp. The... (4 Replies)
Hi All,
I am calling a series of shell scripts via CRON so everything is running as root. However, in my error log file I am seeing the following errors. Please can anyone offer any advise as to the possible causes and solution to prevent the errors from appearing.
The Error 1227 seems to... (2 Replies)
experts, i wrote a python script to do a certain job, i tried it and it is working fine, i want this script to be executed automatically after a ksh script, the problem is when i execute the ksh script my python script runes perfectly after the ksh script as I have include it at the end of the ksh... (1 Reply)
I want to make a config file which contain all the paths.
i want to read the config file line by line and pass as an argument on my below function.
Replace all the path with reading config path line by line and pass in respective functions.
how can i achieve that?
Kindly guide.
... (6 Replies)
Need ideas on how to achieve the below.
We have a script say "profile.sh" which internally calls another existing script called "name.sh" which prompts for the
name and age of a person upon execution. When i run profile.sh how can i populate a pre-defined value from another file and pass that... (1 Reply)
Ceiling Light - The Forgotten Element
One of the highest details concerning using an LED ceiling panel essentially offer a fantastic dance floor which definitely makes the customers dance right away.They are a quite low cost method of something like a lighting solution, simple collection up,... (1 Reply)
Discussion started by: harveyclayton
1 Replies
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
08-23-2013
