01-26-2009
I assume cron is not running - no sign of it in ps output.
This indicates inittab is stalled, probably on a wait command.
Either comment out everything in the inittab, from the last job showing in the console log until the cron entry, and then ad them back one at a time until you find the one blocking the inittab, or add an entry between each line that writes an update to a log file and then the log file should show where inittab stalls.
Or try checking the ps output (ps -ef) for any inittab wait processes still running, then kill them to see if the inittab continues and starts cron.
HTH
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am currently running SCO OpenServer.
When the machine is restart it automatically intitiates processes that allow me to use the ARCserv backup software... Recently, these process were killed and I would like to restart them. The problem is I dont know the name or location of the files invoked... (1 Reply)
Discussion started by: LowOrderBit
1 Replies
2. UNIX for Advanced & Expert Users
Hi Expert,
I have encountered some problem with my SUN system. Everytime when i issue command #init 6 OR #init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init 0..
I can only reboot the system using reboot ... Was... (6 Replies)
Discussion started by: sc2005
6 Replies
3. UNIX for Dummies Questions & Answers
Does anyone know it it is possible to start a program with a timeout, so that it is automatically killed if the timeout expires? If yes, how? (6 Replies)
Discussion started by: soheil.samii
6 Replies
4. SCO
Hello - We have setup printers to startup in the /etc/rc.d/8 directory and when the SCO system is booted this script should kick them off or start them up but it doesn't. So I have to start it from root and leave the window open. I know this isn't right and trying to figure out what's missing. ... (13 Replies)
Discussion started by: dbm7230
13 Replies
5. Linux
Dear all,
I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel):
1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins
So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies
6. Red Hat
What is the difference between 'init s' and 'init 1'.
I know that both will work to change the current run level to single user mode.
Is there any difference in those two commands? (5 Replies)
Discussion started by: praveen_b744
5 Replies
7. Solaris
Hi All,
I am getting an error message when I execute command “zlogin -C sunsrv4z5” on my root server.
INIT: Cannot stat /etc/inittab, errno: 2
INIT: Cannot stat /etc/inittab, errno: 2
As per my analysis it seems that some files inside /etc folder are deleted.
This server was... (14 Replies)
Discussion started by: surbhit4u
14 Replies
8. UNIX for Advanced & Expert Users
Hi,
I am experiencing a weird thing on my SUNFIRE machine with Solaris 9 OS.
When I do init 0 to shutdown the machine to go to ok prompt, what it did was shutdown and reboot like an init 6 command do. I did check the corresponding rc scripts that were involved with init 0 and compared with rc... (2 Replies)
Discussion started by: Yenthanh
2 Replies
9. Solaris
i did my research in finding the answer but couldn't find right one. Please give your inputs. (6 Replies)
Discussion started by: ranumala
6 Replies
10. Red Hat
I encountered a problem on one of our database servers.
OS: CentOS 5.5 final
Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel)
We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies
LEARN ABOUT OSF1
volinstall
volinstall(8) System Manager's Manual volinstall(8)
NAME
volinstall - Sets up Logical Storage Manager (LSM) environment after LSM installation
SYNOPSIS
/usr/sbin/volinstall
DESCRIPTION
The volinstall script sets up LSM special device files, and add the following lines to the /etc/inittab file:
lsmr:s:sysinit:/sbin/lsmbstartup -b </dev/console >/dev/console 2>&1 lsm:23:wait:/sbin/lsmbstartup -n </dev/console >/dev/console 2>&1
vol:23:wait:/sbin/volreconfig -n </dev/console >/dev/console 2>&1
The first line calls the /sbin/lsmbstartup script, which enables LSM to start automatically on system reboot. The second line calls the
/sbin/volreconfig script, which handles any pending encapsulation requests.
If /sbin/lsmbstartup is not added to the /etc/inittab file, LSM must be started manually after system reboot.
Note
The volinstall script is automatically invoked by the volsetup, clu_create, and clu_add_member commands. Therefore, running the volinstall
script to set up LSM is usually not necessary.
SEE ALSO
inittab(4), lsmbstartup(8), volencap(8), volintro(8), volsetup(8),
volinstall(8)