Redirect stdout and stderr to a log file to check what went wrong.
Try having set -x in the script and have the crontab entry like this
Examine the /tmp/log for any clues.
--ahamed
Hi ahamed,
I got the problem. The output of running that jar file is a csv file. When I manually trigger the script, it understands to save the output file in the current folder. However if being trigger by a cron job, it doesn't know where to save the output file to?
Hi All,
I created a shell script and it works perfectly fine when I run from the command. But the same does not work as expected when I call it from a cron job.
Here is the shell script(scan.sh):
#
#
#Which directory to scan for files?... (7 Replies)
Hello, I have the following crontab entry that does not seem to be running. When I check /var/cron/log, it is not there. Here is my os info:
SunOS birch 5.9 Generic_118558-09 sun4u sparc SUNW,Sun-Fire-V240
Here is the crontab entry:
01 21 * * * find /export/app/datafeed/flus/archive -mtime... (5 Replies)
I set up a new cron job. I have set cron jobs many times in the past and never faced issues. For some reasons my new cron job is not working.This is how my cron job looks like. plz help me out guys.
3,8,13,18,23,28,33,38,43,48,53,58 * * * * /siebel/sblp900/home/FSMTaskChk/script... (14 Replies)
Hello,
I have written a script that has a sudo command to change file permissions within it.
When I run the script manually, the sudo command inside of it works fine.
When the script is run through crontab I get the error "cron: not found".
It the same user profile that I am using... (6 Replies)
Hi Gurus,
I have a test unix server in which currently some unix cronjob are running.
I have written two script one is a shell script in which env variable are there (in that i am exporting those variables).
I have also written a perl script .
when i am running at the shell manually like... (5 Replies)
Hi,
I have created a cron job on IBM AIX but it is not working in desired manner !
Here are the steps which I have followed :-
#!/bin/ksh
#------------------------------------------------------------------
find /some/file/at/the/user/side/test.log -exec cp {}... (8 Replies)
cron process in AIX is there when I do ps -ef |grep cron, but none of cron job is working. It appears that cron process is hanging or having some issues? How do you resolve this? Do I kill the cron process by kill -9 PID? and how to start it?
Please advise. (1 Reply)
Hi All,
I have a many cron jobs scheduled in my AIX server.
Only one cron not getting executed in the same server but that job is good on all other servers.
Here is my cron , which will keep last 30 files and remove others.,
00 00 * * * /usr/bin/find /tmp/reports/nmon -name *.nmon -mtime... (9 Replies)
I have put a cron entry in oracle user for taking hot backup every wednesday@ 2.30 AM and have given the cron entry
30 02 * * 3 /u01/vijay/hotbackupcron 2>&1 >> /u01/vijay/hotbackup.log
also find below the script inside hotbackupcron, i have put in env variables as well
... (13 Replies)
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
LEARN ABOUT DEBIAN
inoticoming
INOTICOMING(1) INOTICOMING INOTICOMING(1)NAME
inoticoming - trigger actions when files hit an incoming directory
SYNOPSIS
inoticoming [ global-options ] directory actions*
DESCRIPTION
Inoticoming is a daemon to watch a directory with Linux's inotify framework and trigger actions once files with specific names are placed
in there.
For example it can be used to wait for .changes files uploaded into a directory and call reprepro to put them into your repository.
GLOBAL OPTIONS --foreground
Do not fork, but stay in the foreground and log to stderr.
--logfile filename
After forking in the background, log to the specified filename instead of syslog.
--pid-file filename
Write the pid of the running instance into filename.
--initialsearch
First search the directory for files already existing and process them with the given rules as if they just appeared. If files show
up in this inital phase, they may be processed twice, but should never be missed. (Unless they are too many and the inotify queue
overflows).
ACTIONS
Each action description is an optional list of options for this action (which files to call it for, what directory to change into before
executing it, ...), followed by the command and its arguments ended with a single ; as argument. Like:
inoticoming --foreground / --regexp ^v echo There appeared {} in the root directory. ; (Note that the before the ; is needed if and only
if you calling it from a shell or anything else interpreting the ; on its own).
ACTION OPTIONS
--prefix string
Only trigger this action, if the filename starts with the specified string.
--suffix string
Only trigger this action, if the filename ends with the specified string.
--regexp regular expression
Only trigger this action, if the filename matches the specified regular expression.
--chdir directory
Change into directory before executing the specified commands. (Note that since it is a well-behaved daemon, its working directory
is / which will be inherited by all actions).
--stdout-to-log
Redirect the command's output (stdout) to the logfile.
--stderr-to-log
Redirect the command's error output (stderr) to the logfile.
EXAMPLES
inoticoming --logfile logs/ilog --pid-file pid $INCOMINGDIR --suffix .changes --stderr-to-log reprepro -s -b $REPREPROBASEDIR --waitforlock
1000 processincoming rulename {} ;
This will call reprepro for every new .changes file. Note that giving {} as argument to processincoming (which inoticoming will
replace with the filename) so that only that .changes file is processed and reprepro will not complain about a possible other yet
incomplete .changes file is only available starting with reprepro version 2.2.2.
PROBLEMS
There is no handling of queue overflows yet.
REPORTING BUGS
Report bugs or wishlist requests to the Debian BTS
(e.g. by using reportbug inoticoming under Debian)
or directly to <brlink@debian.org>.
COPYRIGHT
Copyright (C) 2007 Bernhard R. Link
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
inoticoming 2007-08-18 INOTICOMING(1)