cat: ues1.txt_20170530: No such file or directory
cat: ues2.txt_20170530: No such file or directory
cat: ues3.txt_20170530: No such file or directory
cat: ues4.txt_20170530: No such file or directory
cat: ues5.txt_20170530: No such file or directory
cat: ues6.txt_20170530: No such file or directory
Hi
I have written a shell script(in Solaris) in which following logic is there.....
i=1
while read control
do
key=`echo $control | awk -F$DELIMITOR '{ print $1 }'`
echo "Key Values" ${key}
i=`/usr/bin/expr $i + 1`
done < $CONFPATH/$CONFFILE
when i execute it at prompt it... (4 Replies)
I am trying to schedule FTP script through autosys.The scripts works perfectly fine in unix environment.All the run time parameters are evaluated in the profile.Both are unix servers.
But the strange thing is that the script is not getting executed through autosys and it returns success and... (1 Reply)
Hi all,
I wrote small script for Solaris and when I am running it through command prompt its ok, but when I trying to run it using crontab, i am getting error like:
ld.so.1: dbloader: fatal: libACE.so: open failed: No such file or directory
/tmp/file.sh: line 5: 8304 Killed ... (4 Replies)
Hi,
I have script which is properly running but when i schedule it in cron it throws an error like :
Your "cron" job on retrprdapp1
/usr/bin/sh /retr/cron/ftp.sh 2>&1
produced the following output:
/retr/cron/ftp.sh: syntax error at line 17: `(' unexpected
line17 is
# Get list of... (10 Replies)
Hi,
I have the below job scheduled in crontab. Can you please tell me at what interval this job is scheduled? Where is the name of the job defined here? I will definitely go through the UNIX documentation a little later, for the time being, please provide me few details on this. Thank you.
... (0 Replies)
Hi all,
I'm working to a script with /bin/bash shebang.
The script works perfectly if I run from command line.
The script runs under a non root user and inside the commands are set with sudo command in a such a way they can be run under root, for example (first rows of the script):... (5 Replies)
i have a job scheduled in crontab. The problem is, it is not running automatically as per the time scheduled. But runs when executed manually. What would be the problem? Help me with this please. (6 Replies)
Hi Forum,
Good Day!
I have created an empty html file wtih permissoin 777
created shell script(with permission 777) , code is below.
#=======================start==============
. /data09/oracle/apps_st/appl/D_oraapp095.env
rm -rf /home/mnp/Test_log.txt
echo... (1 Reply)
Hi,
We have created a script that's checks the latency of IIDR subscription by fetching details from a config file (that contains subscription details) and running the CHCCLP command. The out put is then concatenated in a csv file. Once all subscription details are saved the script send a mail... (7 Replies)
Discussion started by: ab095
7 Replies
LEARN ABOUT SUSE
cron
CRON(8) System Manager's Manual CRON(8)NAME
cron - daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-l load_avg] [-n]
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'. The -n option
changes this default behavior causing it to run in the foreground. This can be useful when starting it out of init.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if
time has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
PAM Access Control
On SUSE LINUX systems, crond now supports access control with PAM - see pam(8). A PAM configuration file for crond is installed in
/etc/pam.d/crond . crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files.
Naturally this is not relevant if cron was built to use syslog(3).
CAVEATS
In this version of cron, /etc/crontab must not be writable by any user other than root. No crontab files may be links, or linked to by any
other file. No crontab files may be executable, or be writable by any user other than their owner.
SEE ALSO crontab(1), crontab(5), pam(8)AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 10 January 1996" CRON(8)