12-19-2012
Expertise advice required <<URGENT>>
i hav a shell script in my linux server, i want to execute it everyday once automatically without using cron tabs as i dont hav permission to create one.
So wht sld i do??
10 More Discussions You Might Find Interesting
1. Cybersecurity
Dear All,
I have finished my MS in chemical engineering from US university and presetly on OPT work permit.
I do not have software background.
I have received call from consultant company.
They are offering me AIX UNIX training for four weeks and find me a job.
My question is how difficuilt... (0 Replies)
Discussion started by: saarth_desh
0 Replies
2. UNIX for Dummies Questions & Answers
Dear All,
I have finished my MS in chemical engineering from US university and presetly on OPT work permit.
I do not have software background.
I have received call from consultant company.
They are offering me AIX UNIX training for four weeks and find me a job.
My question is how difficuilt... (5 Replies)
Discussion started by: saarth_desh
5 Replies
3. UNIX for Dummies Questions & Answers
Hi UNIX Gurus,
I have got the following requirement and totally :confused: how to proceed.
A file is dummy.lst is there in the following format:--
ID NAME TYPE_ID
-------- --------- -----------
1947 Asia ... (1 Reply)
Discussion started by: rahul26
1 Replies
4. Shell Programming and Scripting
I have a text file, with a fixed format of certain data.
I have to extract certain fields of data.
Then store it in a structure.
Is it possible to use shell commands by making a system call from a C PROGRAM and then store the extracted data in the structure (which has been declared in the C... (1 Reply)
Discussion started by: umanglalani
1 Replies
5. Programming
what does the statement :
static char a = "a";
store in the executable image. ??
I need to make a command line parameter exist AFTER the program finishes execution.. so that when i run the code next time ( without recompiling ).. i can work with the paramter..
for example:
... (5 Replies)
Discussion started by: a.k.aFireknight
5 Replies
6. Solaris
Hi all,
For the past 3 days I have been struggling like :mad: to setup a VNC system between a solaris 8 unix host server and a windows XP tightvnc client viewer.
Please bear in mind that the unix machine is crap & probably should be taken to the "Antiques Road Show on the BBC". Everything is... (2 Replies)
Discussion started by: fawqati
2 Replies
7. Shell Programming and Scripting
Any experts on regular expressions out there, can you help me rationalise this?
In this post: -
https://www.unix.com/shell-programming-scripting/121977-writing-algorithm-recode-data-points-2.html
I use the code: -
tmp = $1 ; gsub(/00/, ".") ; $1 = tmp
tmp = $1 ;... (2 Replies)
Discussion started by: steadyonabix
2 Replies
8. Shell Programming and Scripting
Hi all, this is my first post, so please be gentle...
I have a situation wherby I need a script that traverses known paths. Check for the modified date (n days) and then deletes all subdirs.
I have come up with this hotch potch, but as far as I can tell it seems to work.
What I am wondering... (4 Replies)
Discussion started by: primus7
4 Replies
9. UNIX for Advanced & Expert Users
Dear friends,
Before putting my questions forward, I would like to put some data infront of you, hope you will help me at the end.
This website
Cray-Cyber - Welcome
provides free access to many supercomputers and mainframe computers. When you login through ssh, they provide you with a screen,... (0 Replies)
Discussion started by: gabam
0 Replies
10. Programming
Dear friends,
Before putting my questions forward, I would like to put some data infront of you, hope you will help me at the end.
This website
Cray-Cyber - Welcome
provides free access to many supercomputers and mainframe computers. When you login through ssh, they provide you with a screen,... (5 Replies)
Discussion started by: gabam
5 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-n] [-x debugflags]
DESCRIPTION
cron is normally started during system boot by rc.d(8) framework, if cron is switched on in rc.conf(5).
It will return immediately so you don't have to start it with '&'.
cron searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd. Crontabs found are loaded into memory. cron
also searches for /etc/crontab which is in a different format (see crontab(5)). Finally cron looks for crontabs in /etc/cron.d if it exists,
and executes each file as a crontab.
When cron looks in a directory for crontabs (either in /var/cron/tabs or /etc/cron.d) it will not process files that:
- Start with a '.' or a '#'.
- End with a '~' or with ``.rpmsave'', ``.rpmorig'', or ``.rpmnew''.
- Are of zero length.
- Their length is greater than MAXNAMLEN.
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
executing 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).
Events such as START and FINISH are recorded in the /var/log/cron log file with date and time details. This information is useful for a num-
ber of reasons, such as determining the amount of time required to run a particular job. By default, root has an hourly job that rotates
these log files with compression to preserve disk space.
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab or /etc/cron.d) 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 when-
ever a crontab file is modified. Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
The following options are available:
-x This flag turns on some debugging flags. debugflags is comma-separated list of debugging flags to turn on. If a flag is turned on,
cron writes some additional debugging information to system log during its work. Available debugging flags are:
sch scheduling
proc process control
pars parsing
load database loading
misc miscellaneous
test test mode - do not actually execute any commands
bit show how various bits are set (long)
ext print extended debugging information
-n Stay in the foreground and don't daemonize cron.
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.
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. Natu-
rally this is not relevant if cron was built to use syslog(3).
FILES
/var/cron/tabs cron spool directory
/etc/crontab system crontab file
/etc/cron.d/ system crontab directory
/var/log/cron log file for cron events
SEE ALSO
crontab(1), crontab(5)
AUTHORS
Paul Vixie <vixie@isc.org>
BSD
October 12, 2011 BSD