OK, here's a quick hacked-together version of a script that more-or-less does what crond would do. As Neo has mentioned however, this is not the best idea, as you're kind of needlessly re-inventing something that already exists and which will definitely do a far better job than this shell script. If the customer/client/maintainer/whoever actively doesn't want you running scheduled tasks on the server, then they're not going to be happy about you doing it no matter how you go about doing it. Alternatively if you have a hard requirement to run scheduled tasks and the customer just doesn't want you installing software, then you need to have a conversation with your customer explaining that they need to install crond to enable you to do the work that you've been asked to do, otherwise you can't do it. If the job you need to do has a 100% requirement for scheduled tasks, then whoever provides this system either has to install or let you install crond, or they need to accept that the job can't be done since they won't let you have the tools you need to do it.
Anyway - bearing in mind all the above caveats (and the potential no doubt for bugs and issues that could be lurking with this approach), here's a quickly knocked-together script that would do more or less what you need.
These 2 Users Gave Thanks to drysdalk For This Post:
When logged in as root if I type "env" there are a bunch of environment settings including one for CLASSPATH. However, I ran a cron script that ran this command "env > cronEnv". I noticed that the environment variables were entirely different inside the script. There wasn't even a CLASSPATH... (2 Replies)
I've got an *extremely* simple script I want to run every minute:
#!/bin/sh
ping -c 1 192.168.1.20 > ~/onlinestatus.txt
So, the script is called "status", it's executable, and in the correct path, etc. In a terminal window (I'm using Mac OS X), I can type status, and it will create... (4 Replies)
hello
I use a script to give me the number of users, at each hour.
this script read a file where there is the number of users for each hour and for each month (so 12 files per year).
If i execute the script (root), it is ok, i have xxx users for each hour.
if I put the script in the cron... (1 Reply)
guys
i have written a very simple script .it runs manually well.
but when i put it in cron,it doesn't give the desired output.
script looks like this:
#! /usr/bin/sh
#script for loading data in table using ctl file/Abhijeet K/08.07.2006
/svm_wl1/. .profile
cd... (5 Replies)
I want to cron one script which should run every second Thursday (in general Nth occurence of any day) of every month.
I am not getting the exact idea of doing this; Please guide.
Regards, (3 Replies)
Good morning. I am searching for "how-to"'s for some particular questions:
1. How to write a script in HP-UX 11.
2. How to schedule a script.
3. How to "call" scripts from the original script.
4. How to su to another user from within a script.
This is the basics of what the... (15 Replies)
Dear All,
I have an assignment about collecting /var/adm/messages on each server running Solaris 9. All these servers will be installed with a script that collect all the messages in cron. All the messages will be collected by a single server.
I have a script to collect all the messages, but... (2 Replies)
This has to be the ultimate newbie question...
I have a script that works well. To run it, I cut and paste it into a putty session.
Is there a way to put the script into a file and just run that file -- like a DOS batch file?
I'd like to schedule the file to run daily.
Thanks,... (3 Replies)
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... (3 Replies)
I have a script that require input from terminal at some point (either a,b or c)
How can I cron the script and automatically assume c as the input. (2 Replies)
Discussion started by: aydj
2 Replies
LEARN ABOUT XFREE86
cron
cron(1M) System Administration Commands cron(1M)NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)