02-18-2008
Go to SCO's web site
Panic/Crash Analysis if a dump is available.
Print this article.
The next time the system crashes,
When you reboot do not delete the dump.
When the system is up, run the following:
#crash -d /dev/swap
Follow the steps in the article to determine which program is causing the problem.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a monitoring script that checks on the content of an alert file, I'm doing some checks on weather I have already reported on the alert (there is one alert per file). If I find that the content is the same as before how can I stop and restart the loop until there is differences bewteen the... (5 Replies)
Discussion started by: nhatch
5 Replies
2. Shell Programming and Scripting
Hello,
I host a couple of Call of Duty gameing servers. There are some hackers who love the crash them. When they crash them it simply causes a segmentaion fault and kills the PID. I was wondering it you could help me write a script to simply restart the program after it has been crashed. The... (9 Replies)
Discussion started by: Phobos
9 Replies
3. UNIX for Dummies Questions & Answers
:confused: Everytime our UNIXWARE 7 Server is restarted we also have to restart the spooler. If the spooler is not restarted, print jobs get stuck in the queu. Once restarted by using the following command lpstop and lpstart everything works fine.
Does anyone have any ideas what could be causing... (0 Replies)
Discussion started by: Yorgy
0 Replies
4. Solaris
Hello people,
My solaris server is rebooting, not sure how!!! Which log should I look in to? I checked /var/adm/messages and dmesg also. How do I check older dmesg logs? I checked lastlog and also ran the last command. Nothing useful pointing to why server rebooted.
Also when server reboots I... (4 Replies)
Discussion started by: rcmrulzz
4 Replies
5. Shell Programming and Scripting
Hi Frens,
I want to list some files from a directory, which contains "DONE" in their name, i am receiving files every minute. In this i want to list all the files which are newer than 6 hours but older than 3 hours, of current time
i dont want my list to contain the latest files which are ... (4 Replies)
Discussion started by: Prat007
4 Replies
6. Programming
Hi,
I use gfortran to run the code. Some times I need to stop the program
and restart it. On restarting I need to run the program from the beginning.
Is there any script or option available to restart the program from where
it stopped? This script/option will be immensely useful for... (2 Replies)
Discussion started by: rpd25
2 Replies
7. UNIX for Dummies Questions & Answers
Hi,
How is it possible to restart only your process. I can get the process killed but I am not able to start it.
For eg : i first did this ps -ef|grep _out --displays all the process with _out in the name
then I killed kill -15 36044 -- process id.
Now how can i start the same... (1 Reply)
Discussion started by: TH3M0Nk
1 Replies
8. Shell Programming and Scripting
Hi friends,
I have one unix command which is used to check the network status manually.
followig is the command
check_Network this command give follwoing status
Network 1 is ok
Network 2 is ok
network 3 is ok
network 4 is ok
.
.
.
.
Network 10 is... (8 Replies)
Discussion started by: Nakul_sh
8 Replies
9. SuSE
Environment: SUSE 10.3
I made a configuration change in '/etc/syslog-ng/syslog-ng.conf' file in a server.
An article found on web says "After the change '/etc/init.d/syslog-ng' should be restarted". But there is no 'syslog-ng' in /etc/init.d directory.
What is syslog-ng or a... (4 Replies)
Discussion started by: JDBA
4 Replies
LEARN ABOUT NETBSD
poweroff
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
reboot, poweroff, halt -- restarting, powering down and stopping the system
SYNOPSIS
halt [-dlnpqvxz]
poweroff [-dlnqvxz]
reboot [-dlnqvxz] [arg ...]
DESCRIPTION
The poweroff, halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM, wait for up to 30 seconds
for them to die, send a SIGKILL to the survivors and, respectively, power down, halt or restart the system. The action is logged, including
entering a shutdown record into the login accounting file and sending a message via syslog(3).
The options are as follows:
-d Create a dump before halting or restarting. This option is useful for debugging system dump procedures or capturing the state of a
corrupted or misbehaving system.
-l Suppress sending a message via syslog(3) before halting or restarting.
-n Do not flush the file system cache. This option should be used with extreme caution. It can be used if a disk or a processor is on
fire.
-p Attempt to powerdown the system. If the powerdown fails, or the system does not support software powerdown, the system will halt.
This option is only valid for halt.
-v To enable verbose messages on the console, pass the boothowto(9) flag AB_VERBOSE to reboot(2).
-x To enable debugging messages on the console, pass the boothowto(9) flag AB_DEBUG to reboot(2).
-z To silence some shutdown messages on the console, pass the boothowto(9) flag AB_SILENT to reboot(2).
-q Do not give processes a chance to shut down before halting or restarting. This option should not normally be used.
If there are any arguments passed to reboot they are concatenated with spaces and passed as bootstr to the reboot(2) system call. The string
is passed to the firmware on platforms that support it.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom.
SEE ALSO
reboot(2), syslog(3), utmp(5), boot(8), init(8), rescue(8), shutdown(8), sync(8)
HISTORY
A reboot command appeared in Version 6 AT&T UNIX.
The poweroff command first appeared in NetBSD 1.5.
CAVEATS
Once the command has begun its work, stopping it before it completes will probably result in a system so crippled it must be physically
reset. To prevent premature termination, the command blocks many signals early in its execution. However, nothing can defend against delib-
erate attempts to evade this.
This command will stop the system without running any shutdown(8) scripts. Amongst other things, this means that swapping will not be dis-
abled so that raid(4) can shutdown cleanly. You should normally use shutdown(8) unless you are running in single user mode.
BUGS
The single user shell will ignore the SIGTERM signal. To avoid waiting for the timeout when rebooting or halting from the single user shell,
you have to exec reboot or exec halt.
BSD
February 16, 2011 BSD