09-02-2005
Init 6 & Init 0 problem
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 wondering what happen to the system ???
Unable to find any solution from the SUN website..
Appreciate anyone can help...
10 More Discussions You Might Find Interesting
1. Linux
Hi,
I am using RHEL4 and I am not booting my computer into graphics mode
i.e. It gets hangs after the step of Enabling swap space...
I.e system is not able to enter into runlevel 5.
However, when I boot it into 'runlevel3' and then I do "#startx",
It enetrs... (1 Reply)
Discussion started by: jagdish.machhi@
1 Replies
2. Solaris
root@test09 # ls -al /sbin/init
-r-xr-xr-x 1 root sys 550000 Jun 29 2002 /sbin/init
root@test09 # ls -al /usr/sbin/init
-r-xr-xr-x 1 root sys 37100 Jun 29 2002 /usr/sbin/init (2 Replies)
Discussion started by: userking
2 Replies
3. UNIX for Dummies Questions & Answers
I know if a parent process exits before its child, the last one becomes orphan for a while and then is added to the children of Init process.
I'd like to know deeper
1 how the orphan becomes init process,
2 how init knows that from a some point on it has another child.
Thank you in advance. (2 Replies)
Discussion started by: Puntino
2 Replies
4. Shell Programming and Scripting
Greetings,
I've visited this forums for a long time and normally got an right answer but this time my problem doesn't seem to go away. What I'm trying to do is the following:
VAR="\n\nline1\nline2\nline3\nline4\nline5\nline6\nline7\n\n"
(The count of newlines is varying!)
If I echo this i... (3 Replies)
Discussion started by: ph1l
3 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
what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 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 FREEBSD
reboot
REBOOT(2) BSD System Calls Manual REBOOT(2)
NAME
reboot -- reboot system or halt processor
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
#include <sys/reboot.h>
int
reboot(int howto);
DESCRIPTION
The reboot() system call reboots the system. Only the super-user may reboot a machine on demand. However, a reboot is invoked automatically
in the event of unrecoverable system failures.
The howto argument is a mask of options; the system call interface allows the following options, defined in the include file <sys/reboot.h>,
to be passed to the new kernel or the new bootstrap and init programs.
RB_AUTOBOOT The default, causing the system to reboot in its usual fashion.
RB_ASKNAME Interpreted by the bootstrap program itself, causing it to prompt on the console as to what file should be booted. Normally,
the system is booted from the file ``xx(0,0)kernel'', where xx is the default disk name, without prompting for the file name.
RB_DFLTROOT Use the compiled in root device. Normally, the system uses the device from which it was booted as the root device if possible.
(The default behavior is dependent on the ability of the bootstrap program to determine the drive from which it was loaded,
which is not possible on all systems.)
RB_DUMP Dump kernel memory before rebooting; see savecore(8) for more information.
RB_HALT the processor is simply halted; no reboot takes place. This option should be used with caution.
RB_POWEROFF After halting, the shutdown code will do what it can to turn off the power. This requires hardware support.
RB_INITNAME An option allowing the specification of an init program (see init(8)) other than /sbin/init to be run when the system reboots.
This switch is not currently available.
RB_KDB Load the symbol table and enable a built-in debugger in the system. This option will have no useful function if the kernel is
not configured for debugging. Several other options have different meaning if combined with this option, although their use
may not be possible via the reboot() system call. See ddb(4) for more information.
RB_NOSYNC Normally, the disks are sync'd (see sync(8)) before the processor is halted or rebooted. This option may be useful if file
system changes have been made manually or if the processor is on fire.
RB_RDONLY Initially mount the root file system read-only. This is currently the default, and this option has been deprecated.
RB_SINGLE Normally, the reboot procedure involves an automatic disk consistency check and then multi-user operations. RB_SINGLE prevents
this, booting the system with a single-user shell on the console. RB_SINGLE is actually interpreted by the init(8) program in
the newly booted system.
When no options are given (i.e., RB_AUTOBOOT is used), the system is rebooted from file ``kernel'' in the root file system of unit 0 of a
disk chosen in a processor specific way. An automatic consistency check of the disks is normally performed (see fsck(8)).
RETURN VALUES
If successful, this call never returns. Otherwise, a -1 is returned and an error is returned in the global variable errno.
ERRORS
[EPERM] The caller is not the super-user.
SEE ALSO
crash(8), halt(8), init(8), reboot(8), savecore(8)
HISTORY
The reboot() system call appeared in 4.0BSD.
BUGS
The HP300 implementation supports neither RB_DFLTROOT nor RB_KDB.
BSD
June 4, 1993 BSD