06-16-2011
Quote:
Originally Posted by
cyberkingjk
Which log or commands should be used to analyse the reboot incident?
Start with inspecting the crontabs.
Quote:
Originally Posted by
cyberkingjk
Please explain in detail.
Consult the man page of "cron" and "crontab" for details.
I hope this helps.
bakunin
This User Gave Thanks to bakunin For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
All,
Does anybody know of a Unix command or file name where I can find out when the Unix box was last rebooted?
We're using HP-UX 10.2.
Thanks,
PP (3 Replies)
Discussion started by: Positive Parrot
3 Replies
2. AIX
Dear Gurus,
I would like to know if fsck is executed automatically during reboot for AIX?
Is there any logs which I can refer to? or any documentation reference for this?
Thank You. (2 Replies)
Discussion started by: cteoh88
2 Replies
3. AIX
is it possible to find out memory frequency(speed) in vio server in aix?
Regards
Manoj (0 Replies)
Discussion started by: manoj.solaris
0 Replies
4. AIX
Hi,
I am a newbie to AIX. We have 2 AIX5.3 servers in our environment, I need to transfer some files in Binary mode from one server to another and some files in ASCII mode from one server to another server. Could you please help me as to how I need to do that?
Thanks,
Rakesh (4 Replies)
Discussion started by: rakeshc.apps
4 Replies
5. AIX
Hello I'm new to this Forum and I've got a big Problem.
Currently I have to Install Bacula ( Backup Software) on a IBM machine(with AIX 5.3) via SSH there is no chance for me for a directly interaction with the Server.
The Main problem is, I don't have Root access and no chance to get it.
And... (5 Replies)
Discussion started by: maxkoch
5 Replies
6. Shell Programming and Scripting
Hi,
We have hosted our application on AIX server. The problem is that we have to start our application manually once the server is rebooted. Please guide me in writing a script that does this job automatically with the re-start of the server. I'm looking for something like windows services in... (2 Replies)
Discussion started by: himanshu397
2 Replies
7. Shell Programming and Scripting
Hi friends,,,
I am running one server on Ubuntu 12.04 LTS 32-bit, some times my pc restarts automatically, with no reason, I have a script to start server which requires root password. in this directory
/myserver/start_server.sh
How can I do this ?
and some scripts I am having that I... (1 Reply)
Discussion started by: Akshay Hegde
1 Replies
8. AIX
Hello Everyone,
Can you please help me with the following questions regarding recycling LPARs.
1) Is it recommended to automate the reboot of AIX LPARs with a script ?
i mean we've few App LPARs and Database LPARs. we would like to bring down LPARs on last sunday of every month for about 1... (4 Replies)
Discussion started by: System Admin 77
4 Replies
9. AIX
Hi All,
I am trying to find out type of AIX servers , for eg : server A is eServer p5 520 , server B is pSeries 630-6C4 etc.
Can some one suggest me the best way to retrive this information through command line.
is there any direct command or script by which i can retrieve this information... (9 Replies)
Discussion started by: omkar.jadhav
9 Replies
10. Solaris
Hi,
anyone please let us know how to write shell script to find the missing mountpoints after server reboot.
i want to take the mountpount information before server reboot, and validate the mountpoints after server reboot if any missing.please let us know the shell script from begining to end as... (24 Replies)
Discussion started by: VenkatReddy786
24 Replies
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)