06-02-2009
Need help to identify the flags by scripts.
Hi,
I have two different scripts sap_ftp.sh and sap_ftp_dd.sh which are running continously in background. I am using another script called start.sh to launch these two scripts.
Either one script will process files at a time . During that time other script will sleep.. Each script will create corresponding flag file while processing files
sap_ftp.sh script checks weather sap_ftp_dd.sh flag exists or not. If flag exists this script will go to sleep for 10 secs. After that again it wakes up and checks flag exists or not, If it does not sap_ftp.sh starts processing the files by creating the flag file.
This is same for sap_ftp_dd.sh . This scritp also checks is there any (sap_ftp.sh) flag exists. If this does not exists, it will start processing files or else goes to sleep for 10 secs..
I am facing a problem while identifying the flags...
Since i am launching both the scripts through different script. Both are getting launch at a time.. Both are checking for the flags. Both are not finding any thing. Both are inserting the flags at a time and both are deleting the flags at a time.
I tried launching the second script delayed by few seconds. but that also did not worked out..
kindly help me how can i able to make scripts to identify the flag.
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi folks.
I'm just starting to teach myself shell scripting and am having some trouble with an if statement. I am working with a directory where only one file will reside at a time and need to evaluate if this file is compressed to determine subsequent steps. I'm using echo for testing purposes.... (2 Replies)
Discussion started by: kristy
2 Replies
2. Shell Programming and Scripting
Hi,
I found this strange behaviour while using one of the makefiles.
Here is the snippet of the unix.mak that is necessary for this context
SO = SvSocket.o SvStmt.o SvOdbcWrapper.o \
OdbcCallReader.o MgrCalls.o OdbcSvProxy.o \
OdbcSvApp.o... (4 Replies)
Discussion started by: vino
4 Replies
3. UNIX for Dummies Questions & Answers
I have a script which will look for a test folder under the parent directory. If the folder contains test folder then create the same directory structure in other remote machine.
Once the directories are created then transfer all the contents of that test folder.
this is what i am doing :-
... (2 Replies)
Discussion started by: chris1234
2 Replies
4. UNIX for Dummies Questions & Answers
Hello,
I am running into a bit of an issue running a Makefile. The problem is it was written for a xlf90 compiler when I have a pgf90 on the machine. Therefore, I keep getting errors regarding the xlf90 flags because they don't correspond with the pgf90. Here is the code:
... (0 Replies)
Discussion started by: lepagano
0 Replies
5. UNIX for Dummies Questions & Answers
Can anybody actually tell, what is flag? I know they are termed as permission flags and various others.
Please explain (3 Replies)
Discussion started by: nixhead
3 Replies
6. UNIX for Advanced & Expert Users
How to identify the scripts ran at a particular day of last month?
I have to identify a script that ran on 06/01/2011 @ 4 am (3 Replies)
Discussion started by: rdhanek
3 Replies
7. UNIX for Dummies Questions & Answers
Hi there,
I need your help in understanding the below Solaris 10 ifconfig output;
athnetspns02>ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0:... (2 Replies)
Discussion started by: wthomas
2 Replies
8. Shell Programming and Scripting
hello all,
i have the below script that we used to backup our DB using oracle's utility called RMAN. This has been working fine, but the issue is when the backup fails and we re-start it, it backups the whole thing again. Example.
lets say i have 5 database on my system(db1,db2,db3,db4,db5)... (11 Replies)
Discussion started by: crazy_max
11 Replies
9. Shell Programming and Scripting
tr a-z A-Z << END_TEXT
one two three
four five six
END_TEXT
i dont want this to be executed when someone runs the script that this is in. but for some reason, it gets executed. anywhere i can wrap this up in something to make sure it never gets executed?
another example:
cat <<... (1 Reply)
Discussion started by: SkySmart
1 Replies
10. UNIX for Advanced & Expert Users
Hi,
Please let me know if you have any thoughts on how to read a table that has all the oracle sql files or shell scripts at the job and step level to identify all the tables that does merge, update, delete, insert, create, truncate, alter table (ALTER TABLE XYZ RENAME TO ABC) and call them out... (1 Reply)
Discussion started by: techmoris
1 Replies
LEARN ABOUT DEBIAN
dh_installinit
DH_INSTALLINIT(1) Debhelper DH_INSTALLINIT(1)
NAME
dh_installinit - install init scripts and/or upstart jobs into package build directories
SYNOPSIS
dh_installinit [debhelperoptions] [--name=name] [-n] [-R] [-r] [-d] [--params]
DESCRIPTION
dh_installinit is a debhelper program that is responsible for installing init scripts with associated defaults files, as well as upstart
job files into package build directories.
It also automatically generates the postinst and postrm and prerm commands needed to set up the symlinks in /etc/rc*.d/ to start and stop
the init scripts.
FILES
debian/package.init
If this exists, it is installed into etc/init.d/package in the package build directory.
debian/package.default
If this exists, it is installed into etc/default/package in the package build directory.
debian/package.upstart
If this exists, it is installed into etc/init/package.conf in the package build directory.
OPTIONS
-n, --noscripts
Do not modify postinst/postrm/prerm scripts.
-o, --onlyscripts
Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, or upstart job. May be useful if the
init script or upstart job is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it.
-R, --restart-after-upgrade
Do not stop the init script until after the package upgrade has been completed. This is different than the default behavior, which
stops the script in the prerm, and starts it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
-r, --no-restart-on-upgrade
Do not stop init script on upgrade.
--no-start
Do not start the init script on install or upgrade, or stop it on removal. Only call update-rc.d. Useful for rcS scripts.
-d, --remove-d
Remove trailing d from the name of the package, and use the result for the filename the upstart job file is installed as in etc/init/ ,
and for the filename the init script is installed as in etc/init.d and the default file is installed as in etc/default/ . This may be
useful for daemons with names ending in d. (Note: this takes precedence over the --init-script parameter described below.)
-uparams --update-rcd-params=params
-- params
Pass params to update-rc.d(8). If not specified, defaults will be passed to update-rc.d(8).
--name=name
Install the init script (and default file) as well as upstart job file using the filename name instead of the default filename, which
is the package name. When this parameter is used, dh_installinit looks for and installs files named debian/package.name.init,
debian/package.name.default and debian/package.name.upstart instead of the usual debian/package.init, debian/package.default and
debian/package.upstart.
--init-script=scriptname
Use scriptname as the filename the init script is installed as in etc/init.d/ (and also use it as the filename for the defaults file,
if it is installed). If you use this parameter, dh_installinit will look to see if a file in the debian/ directory exists that looks
like package.scriptname and if so will install it as the init script in preference to the files it normally installs.
This parameter is deprecated, use the --name parameter instead. This parameter is incompatible with the use of upstart jobs.
--error-handler=function
Call the named shell function if running the init script fails. The function should be provided in the prerm and postinst scripts,
before the #DEBHELPER# token.
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple
instances of the same text to be added to maintainer scripts.
SEE ALSO
debhelper(7)
This program is a part of debhelper.
AUTHORS
Joey Hess <joeyh@debian.org>
Steve Langasek <steve.langasek@canonical.com>
9.20120909 2012-04-10 DH_INSTALLINIT(1)