Autoexpect with cron

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Execution problem with Cron: Script works manually but not w/Cron. Why?

Hello gurus, I am making what I think is a simple db2 call from within a shell script but I am having difficulty producing the desired report when I run the script shown below from a shell script in cron. For example, my script and the crontab file setup is shown below: #!/bin/ksh db2...

2. Shell Programming and Scripting

Cron job - Need to run Cron every quarter at particular time

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...

3. Shell Programming and Scripting

Commented cron job -- cron monitoring

Hi I have a requirement to write a shell script,that will check the all commented job in cron job.Please help !!

4. Solaris

Cron job running even after cron is removed

Hi , I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility ) I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And...

5. UNIX for Dummies Questions & Answers

How are cron.allow and cron.deny read?

Hi, all! I was working on my Debian, minding my own business but then I wanted to see what happened if the same user was included on both cron.allow and cron.deny :p I would have bet that cron.deny was going to override cron.allow for security reasons, but my computer proved me wrong:...

6. Solaris

User entry in both cron.allow and cron.deny

Hello All, Anybody please help me to know ,what happens when a user having entry in both cron.allow and cron.deny files.Wheather the user will be able to access the crontab??? Thanks in advance Vaisakh

7. Solaris

cron job starts new cron proccess

I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically...

8. UNIX for Dummies Questions & Answers

CRON usage for CRON job

can anybody explain the usage of CRON for adding a cron job. please provide an example also for better understanding !!! Thanks

9. AIX

AIX and cron logs filtering ?: /etc/cronlog.conf, /var/adm/cron/log

Hi, I can use 'crontabs –e' and do all the scheduling I like. However I would like to auto send myself just the cronjobs logs that fail. That is to say the PIDs that fail and the related lines with those PID’s only. (Not the full set of logs) Has anyone done this work? Or does an AIX 5.3 tool...

10. Shell Programming and Scripting

autoexpect

I have created an autoexpect script for an installation cd. The problem is that at a certain point the autoexpect script just hangs i have tried using conservative mode, putting a 1 second sleep before the line where it hangs. Is there any sort of debuging output or how do i get it to...

LEARN ABOUT MOJAVE

crontab

CRONTAB(1)						    BSD General Commands Manual 						CRONTAB(1)

NAME

     crontab -- maintain crontab files for individual users (V3)

SYNOPSIS

     crontab [-u user] file
     crontab [-u user] { -l | -r | -e }

DESCRIPTION

     The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron.  Each user
     can have their own crontab, and they are not intended to be edited directly.

     (Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
     which provides a more flexible way of automatically executing commands.  See launchctl(1) for more information.)

     If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command.  If the
     /usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
     /usr/lib/cron/cron.deny file in order to use this command.  If neither of these files exists, then depending on site-dependent configuration
     parameters, only the super user will be allowed to use this command, or all users will be able to use this command.  The format of these
     files is one username per line, with no leading or trailing whitespace.  Lines of other formats will be ignored, and so can be used for com-
     ments.

     The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.

     The following options are available:

     -u      Specify the name of the user whose crontab is to be tweaked.  If this option is not given, crontab examines ``your'' crontab, i.e.,
	     the crontab of the person executing the command.  Note that su(1) can confuse crontab and that if you are running inside of su(1) you
	     should always use the -u option for safety's sake.

     -l      Display the current crontab on standard output.

     -r      Remove the current crontab.

     -e      Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables.  The specified editor must edit
	     the file in place; any editor that unlinks the file and recreates it cannot be used.  After you exit from the editor, the modified
	     crontab will be installed automatically.

FILES

     /usr/lib/cron/cron.allow
     /usr/lib/cron/cron.deny

DIAGNOSTICS

     A fairly informative usage message appears if you run it with a bad command line.

SEE ALSO

     crontab(5), compat(5), cron(8), launchctl(1)

STANDARDS

     The crontab command conforms to IEEE Std 1003.2 (``POSIX.2'').  The new command syntax differs from previous versions of Vixie Cron, as well
     as from the classic SVR3 syntax.

AUTHORS

     Paul Vixie <paul@vix.com>

BSD
								 December 29, 1993							       BSD

UNIX for Advanced & Expert Users