I have a requirement, where I need to check for file. If file is not available then wait for 5 minutes and if it still not available, fail the process. It should check every one minute.
If File available in between, should start remaining process. Now my problem is, I have both part ready. But not able to understand where to put script logic, if file is available.
Ex: Wait for file, for 5 minutes, check every one minute
Now, if file aa.txt is available at beginning or in between above , then I need to start working on it. I do not know where to keep that portion. Can somebody help me?
---------- Post updated at 09:09 PM ---------- Previous update was at 08:59 PM ----------
Sorry, I found solution. I have posted solution for same in 2008.
Hello,
I am trying to create a file watcher script to check for a file until certain time and throw a message. can some one please help me if there is script handy ??
Thanks,
Sateesh (1 Reply)
My file watcher is scheduled to look for a File ABC.XYZ.
Ideally when it find this file present in the directory it is looking in should end :b:, but this file watcher is wasting 6-9 minutes each day :eek:
i am unable to understand why this file watcher is behaving in freakish manner...:confused: (1 Reply)
Hi
Please help me in this
I want to execute a shell script abc.ksh.
But I only want it to execute if file XYZ is not present.
If file XYZ is present than I want to unix to sleep for 5 Sec and than agaian check for XYX existence.
if it sleeps for more than 30 seconds ( 6 time )I want it to... (3 Replies)
Hi,
Would like to kick off a script based on the file arrival using autosys but this has to monitor every second instead of a minute.
Is there a better way to implement the monitor apart from cronjob and only need to use autosys in UNIX.
Regards,
Rajasilpa (0 Replies)
Hi,
I need a script for "FILE WATCHER"
I have in a remote FTP location server named MAIN _104
EveryDay mrng 8 i hav to search couple of folders(COL, ATT, TRA) in that FTP server (MAIN_104), and if any files are present in that folders i hav to bring back to my computer and store it anywhere... (4 Replies)
Hi Experts
I will have be having 3 types of files in directory
file1_p0_date
file1_p1_date
file1_p2_date
As soon as it sees any of the files it needs to kick off another process and also would need the file name
For this I am creating a file watcher script which will look for file1* My... (2 Replies)
Hi all,
I am writing a script to do the following:
1) Check if there are any new <csv> files (in abc directory) to process
2) If there is new file, then perform some operation on that file.
3) Move it to a different location(after step2 is successful)
4) Do further processing on the file
... (2 Replies)
Hi friends,
Instead of creating a script autosys 11.3 has a feature for filewatcher.
Can anyone please share a link where ican create a file watcher job (more like manual).
i need to create a filewatcher job where the job should search for a file for every 5 mins
and send a mail whether the... (1 Reply)
Hi friends,
I do not have much thoughts so need any help on the below issue:
I need to create shell script that will find the files & throw an error through job (autosys) when file not found.
Daily we use to receive 3 files from a system.
Obstacles:
1) All 3 files names are same.
2)... (4 Replies)
if test -n "$(find/data/path/ 'filename.txst' -print-quit)
then
echo "file found"
exit 0
else
echo "file not found"
exit 46
fi
So I basically looking to understand the
if test -n "$(find/data/path/ 'filename.txst' -print-quit)
line.
Pls help to elaborate what this command... (6 Replies)
Discussion started by: Nsharma3006
6 Replies
LEARN ABOUT X11R4
wait
wait(1) User Commands wait(1)NAME
wait - await process completion
SYNOPSIS
/bin/sh
wait [pid...]
/bin/jsh /bin/ksh /usr/xpg4/bin/sh
wait [pid...]
wait [ % jobid...]
/bin/csh
wait
DESCRIPTION
The shell itself executes wait, without creating a new process. If you get the error message cannot fork,too many processes, try using the
wait command to clean up your background processes. If this doesn't help, the system process table is probably full or you have too many
active foreground processes. There is a limit to the number of process IDs associated with your login, and to the number the system can
keep track of.
Not all the processes of a pipeline with three or more stages are children of the shell, and thus cannot be waited for.
/bin/sh, /bin/jsh
Wait for your background process whose process ID is pid and report its termination status. If pid is omitted, all your shell's currently
active background processes are waited for and the return code will be 0. The wait utility accepts a job identifier, when Job Control is
enabled (jsh), and the argument, jobid, is preceded by a percent sign (%).
If pid is not an active process ID, the wait utility will return immediately and the return code will be 0.
csh
Wait for your background processes.
ksh
When an asynchronous list is started by the shell, the process ID of the last command in each element of the asynchronous list becomes
known in the current shell execution environment.
If the wait utility is invoked with no operands, it will wait until all process IDs known to the invoking shell have terminated and exit
with an exit status of 0.
If one or more pid or jobid operands are specified that represent known process IDs (or jobids), the wait utility will wait until all of
them have terminated. If one or more pid or jobid operands are specified that represent unknown process IDs (or jobids), wait will treat
them as if they were known process IDs (or jobids) that exited with exit status 127. The exit status returned by the wait utility will be
the exit status of the process requested by the last pid or jobid operand.
The known process IDs are applicable only for invocations of wait in the current shell execution environment.
OPERANDS
The following operands are supported:
One of the following:
pid The unsigned decimal integer process ID of a command, for which the utility is to wait for the termination.
jobid A job control job ID that identifies a background process group to be waited for. The job control job ID notation is applicable
only for invocations of wait in the current shell execution environment, and only on systems supporting the job control option.
USAGE
On most implementations, wait is a shell built-in. If it is called in a subshell or separate utility execution environment, such as one of
the following,
(wait)
nohup wait ...
find . -exec wait ... ;
it will return immediately because there will be no known process IDs to wait for in those environments.
EXAMPLES
Example 1: Using A Script To Identify The Termination Signal
Although the exact value used when a process is terminated by a signal is unspecified, if it is known that a signal terminated a process, a
script can still reliably figure out which signal is using kill, as shown by the following (/bin/ksh and /usr/xpg4/bin/sh):
sleep 1000&
pid=$!
kill -kill $pid
wait $pid
echo $pid was terminated by a SIG$(kill -l $(($?-128))) signal.
Example 2: Returning The Exit Status Of A Process
If the following sequence of commands is run in less than 31 seconds (/bin/ksh and /usr/xpg4/bin/sh):
sleep 257 | sleep 31 &
jobs -l %%
then either of the following commands will return the exit status of the second sleep in the pipeline:
wait <pid of sleep 31>
wait %%
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of wait: LANG, LC_ALL, LC_CTYPE, LC_MES-
SAGES, and NLSPATH.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), jobs(1), ksh(1), sh(1), attributes(5), environ(5), standards(5)SunOS 5.10 12 Dec 1997 wait(1)