Thnk you for your answer. after I will try your suggestion
the problem with myscript:
If in the HOTFOLDER there are 10 .xlsx files and then I copy a new one, the loop works all file to the end.
If there is no file inside the HOTFOLDER and then I copy 10.xlsx, the loop processes only one
It is because of the way you were using inotifywait.
will wait for the create event in /some/dir, report that event and exit.
You copy 10 files into that directory and only the first is processed because the script is finished (or at least the wildcard *.xlsx is expanded) before the second file is added.
will run the loop for every file added to the directory /some/dir and will process the files one-at-a-time.
Hello
i am trying to remove a line using an input file , but this depends upon user interaction
here is the sample
#!/bin/sh
echo "Please enter whether you want to remove Profile"
read value1
if ;then
sed /movie/d temp.txt> temp3.txt
else
echo "Script didnot remove profile"
fi
... (3 Replies)
Could some one help me on this... For loop is working...!
for x in $i
do
for y in $j
do
z=`echo $y | awk '{print $2}'`
if
then
FS=`/usr/bin/echo $y`
echo $FS >>$Basic_location/out.csv
fi
done
CPRT="Cpoyright @ BTOIDCIM"
done (3 Replies)
here we go..
While loop is not working file.. It also invokes one more shell scripts for which parameters need to passed on.
while read line
do
####
#### We want to have a logfile for each load
####
PLog="${LogDir}/${Script}.log";
####
... (5 Replies)
Hi
I'm going to write a program in C language to watch activity on file system
in SCO UNIX openserver 5.0.6.
Apparently Linux provide an API called "inotify" , I'm wondering what's the SCO UNIX package for this ? (1 Reply)
hi everyone
i am facing a very strange problem . please help me why my while loop is not working.
below is my code
#!/bin/ksh
file=RCMC_ABC_999_080924_210813.DAR
echo ${file}
value=001
count=10
echo "abc"
echo ${count}
value=$((${value} + 1 ))
echo ${value}
while ]
do
echo... (3 Replies)
I have initiated an inotify process with --fromfile option and the file contain the paths to be monitored.
/usr/local/maldetect/inotify/inotifywait -d -r -o /usr/local/maldetect/inotify/inotify_log --fromfile /usr/local/maldetect/sess/inotify.paths.28364 --exclude (^/var/tmp/mysql.sock)... (2 Replies)
Hello all,
I would like to unzip some files with a for-loop.
Is there anyone who could tell me how I should do this - in a correct way?
for file in $(ls); do echo gzip -d < $file | tar xf -; done
The problem is the pipe - I believe. But how could I do it? I need it for the command... (4 Replies)
I wish to install inotify-tools-3.20.1-2.4.x86_64.rpm on Linux and fire inotifywait command.
Initially i was looking for "inotify-tools-3.xx.tar.gz" as instructed here http://jensd.be/248/linux/use-inotify-tools-on-centos-7-or-rhel-7-to-watch-files-and-directories-for-events
I have... (9 Replies)
Dear members, moderators and others.
While working on <insert project>, a need has surfaced to watch a directory, and when a file comes, to do appropriate action.
So, i started writing some shell code, aware of linux inotify-tools package with inotifywait.
Also, i'm seeing a lot of similar... (1 Reply)
Discussion started by: Peasant
1 Replies
LEARN ABOUT DEBIAN
io::async::timer::periodic
IO::Async::Timer::Periodic(3pm) User Contributed Perl Documentation IO::Async::Timer::Periodic(3pm)NAME
"IO::Async::Timer::Periodic" - event callback at regular intervals
SYNOPSIS
use IO::Async::Timer::Periodic;
use IO::Async::Loop;
my $loop = IO::Async::Loop->new;
my $timer = IO::Async::Timer::Periodic->new(
interval => 60,
on_tick => sub {
print "You've had a minute
";
},
);
$timer->start;
$loop->add( $timer );
$loop->run;
DESCRIPTION
This subclass of IO::Async::Timer implements repeating events at regular clock intervals. The timing may or may not be subject to how long
it takes the callback to execute. Iterations may be rescheduled runs at fixed regular intervals beginning at the time the timer was
started, or by a fixed delay after the previous code has finished executing.
For a "Timer" object that only runs a callback once, after a given delay, see instead IO::Async::Timer::Countdown. A Countdown timer can
also be used to create repeating events that fire at a fixed delay after the previous event has finished processing. See als the examples
in "IO::Async::Timer::Countdown".
EVENTS
The following events are invoked, either using subclass methods or CODE references in parameters:
on_tick
Invoked on each interval of the timer.
PARAMETERS
The following named parameters may be passed to "new" or "configure":
on_tick => CODE
CODE reference for the "on_tick" event.
interval => NUM
The interval in seconds between invocations of the callback or method. Cannot be changed if the timer is running.
first_interval => NUM
Optional. If defined, the interval in seconds after calling the "start" method before the first invocation of the callback or
method. Thereafter, the regular "interval" will be used. If not supplied, the first interval will be the same as the others.
Even if this value is zero, the first invocation will be made asynchronously, by the containing "Loop" object, and not
synchronously by the "start" method itself.
reschedule => STRING
Optional. Must be one of "hard", "skip" or "drift". Defines the algorithm used to reschedule the next invocation.
"hard" schedules each iteration at the fixed interval from the previous iteration's schedule time, ensuring a regular repeating
event.
"skip" schedules similarly to "hard", but skips over times that have already passed. This matters if the duration is particularly
short and there's a possibility that times may be missed, or if the entire process is stopped and resumed by "SIGSTOP" or similar.
"drift" schedules each iteration at the fixed interval from the time that the previous iteration's event handler returns. This
allows it to slowly drift over time and become desynchronised with other events of the same interval or multiples/fractions of it.
Once constructed, the timer object will need to be added to the "Loop" before it will work. It will also need to be started by the "start"
method.
AUTHOR
Paul Evans <leonerd@leonerd.org.uk>
perl v5.14.2 2012-10-24 IO::Async::Timer::Periodic(3pm)