10-24-2002
This should not cause a reboot.
Do you have more information about the reboots?
e.g. like alway at the same day/time, or always when a specific job is running?
when this happens mostly it had to do with the power or rear hardware problems, because otherwise the systems logs the reason of this PANIC reboot.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I wonder how I shall read the result below, especially 'what'
shown below.
The result was shown when I entered 'w'.
E.g what is TOP? What is gosh ( what does selmgr mean?)?
login@ idle JCPU PCPU what
6:15am 7:04 39 39 TOP
6:34am 6:45 45 45 TOP
6:41am ... (1 Reply)
Discussion started by: Aelgen
1 Replies
2. UNIX for Dummies Questions & Answers
echo 'it's friday'
why appear the > (3 Replies)
Discussion started by: yls177
3 Replies
3. Windows & DOS: Issues & Discussions
Hello!
Will someone help me find a solution to my computer systems which as windows 98 and Windows 2000 professional running on it. After shutting down the system the system will prompt system shutdown but it will not power off the system( the system as an ATX power system) . Therefore it is as... (1 Reply)
Discussion started by: kayode
1 Replies
4. UNIX for Advanced & Expert Users
Somehow someone created a file named '-ov' in the root directory.
Given the name, the how was probably the result of some cpio command they bozo'ed.
I've tried a number of different ways to get rid of it using * and ? wildcards, '\' escape patterns etc.. They all fail with " illegal option --... (3 Replies)
Discussion started by: GSalisbury
3 Replies
5. Shell Programming and Scripting
Hopefully this doesn't come off as too much of a "newbie" question or a flamebait. But I have recently begun working with a Sun Solaris box after having spent the past five years working with RedHat. From what i can tell, thing look fairly similar and the 'man' command is some help. But I've... (7 Replies)
Discussion started by: deckard
7 Replies
6. UNIX for Dummies Questions & Answers
Hi,
Can someone advise me how to find the last system rebooted date(s)? Thanx N Regards,
Hush (2 Replies)
Discussion started by: hush
2 Replies
7. Solaris
dear all,
I have 2 T2000 with solaris 10 and oracle 10g installed on it. these two servers are rebooted by itself.
could anyone help me investigate the cause.
the message log is attached
thanx, (3 Replies)
Discussion started by: fsmadi
3 Replies
8. Solaris
Hello Everyone ,
I am a new member to this forum and came to know about this from so many of my friends . I face one issue last day when suddenly the system got rebooted ( But don,t know why ) . Can someone please help me in investigating this issue as to why the system got rebooted and who... (4 Replies)
Discussion started by: gera_sachin125
4 Replies
9. Solaris
Hi all,
i want to know the procedure reboot the server through console if the system is completely down.Please help me if anybody knows this. I would really thanfull to all.
regards
Krishna Murthy (1 Reply)
Discussion started by: murthy76
1 Replies
10. UNIX for Advanced & Expert Users
Hi,
I have two users login on my HPUX i.e user1 and user2.
Inorder to switch from user1 to user2 without password I generated key pair using keygen command for user id user1 and copied the its public key to the .ssh/authorized_keys file of user2.
ssh-keygen -b 2048 -t rsa
This... (5 Replies)
Discussion started by: mohtashims
5 Replies
REBOOT(8) System Manager's Manual REBOOT(8)
NAME
reboot - stopping and restarting the system
SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ]
/sbin/halt [ -lqndars ]
/sbin/fastboot [ -lqndarsRD ]
DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is
necessary to read it in from disk or tape each time it is to be boot strapped.
Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put
the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first.
Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware
time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk
check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation.
Options to reboot are:
-l Don't try to tell syslogd(8) what's about to happen.
-q Reboot quickly and ungracefully, without shutting down running processes first.
-n Don't sync before rebooting. This can be used if a disk or the processor is on fire.
-h Don't reboot, simply halt the processor.
-d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic.
-a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix).
-r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD.
-s Don't enter multi-user mode after system has rebooted - stay in single user mode.
-f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by
passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt)
flag.
-D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program.
-R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the
root/swap/pipe/dump device.
Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are
present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this
case.
Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively.
Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are
intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user
operations.
SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8)
3rd Berkeley Distribution May 24, 1996 REBOOT(8)