10 More Discussions You Might Find Interesting
1. OS X (Apple)
MacPro (2013) 12-Core, 64GB RAM (today's crash):
panic(cpu 2 caller 0xffffff7f8b333ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (318824 seconds ago): 31883, last successful... (3 Replies)
Discussion started by: Neo
3 Replies
2. Linux
Hey everyone. Ok, so I know that from inside of any particular program, it see's through virtualized memory, a full range of available memory. It is given the ability then to place variables, data, user input etc, on the Stack, Heap, BSS, or Code segment of it's range. My question is what does the... (5 Replies)
Discussion started by: Lost in Cyberia
5 Replies
3. AIX
I admin an AIX box for a small company. The time on the AIX machine has to be changed twice a year for DST. I know I can set it to do this automagically but is that a good idea? I have read about people having problems with software databases and cron jobs... Is it possible to sync the AIX machine... (1 Reply)
Discussion started by: herot
1 Replies
4. HP-UX
Hi all,
I have a server running HP-UX 11i V1 (11.11).
We had a problem with the system disk which cannot boot and the recovery with the CD failed too.
the only solution was to re-install the system on a new disk.
The problem now is to get access to the data which are on other disks, not... (2 Replies)
Discussion started by: aribault
2 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
First and foremost I would like to mention I am pretty new to Linux.
I have some experience in Windows systems administration but nothing professionally.
Expect some real newbie questions.
For a small company I am trying to install a server so a development environment can be... (1 Reply)
Discussion started by: Crazy Harry
1 Replies
6. Programming
hello all,
I have developed a server application in C for ulinux kernel 2.6.It works very fine; creating a socket, binding it to a port, listening for incoming sockets and accepting them ,all finish without any error.
But there is a problem regarding application crash.After an intentionally... (1 Reply)
Discussion started by: Sedighzadeh
1 Replies
7. AIX
Hello everyone
I have a partition with the TL 5300-06-01-0000 and try to update to this TL 5300-09-03-0918 but suddenly the update dont work more. I get in to the HMC and I see this code error 888 102 700 0C5
I try to restart my partition but doesnt work.
Theres someone who has this... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies
8. HP-UX
Hi,
First of all, thanks for your help. I have downloaded freeBSD to study unix
I'm here again 'cause my HP-UX 10.x has "broken". It raise this error:
----------------------------------------------------
Diagnostic System warning:
= 0x1f005000 is POWERFAILED The diagnostic logging... (1 Reply)
Discussion started by: efrenba
1 Replies
9. Filesystems, Disks and Memory
I need some expert help, and would appreciate any feedback on the following problem:
After power outage the machine didn't allow the login. When we checked it , it looked like both disks were completely empty. Luckily, we have a backup machine, and we can restore the disks.
Has anybody seen... (3 Replies)
Discussion started by: DGoubine
3 Replies
10. UNIX for Dummies Questions & Answers
Hello All
We are using Tru64 Unix V4.0D on a Digital Alpha 1200 machine, which by coincidence, crashed last night! Completely out of the Blue!!! After rebooting the system and recovering the databases everything seemed to work ok. It is however, discomforting not to know how or why the system... (2 Replies)
Discussion started by: Ivo
2 Replies
savecore(1M) System Administration Commands savecore(1M)
NAME
savecore - save a crash dump of the operating system
SYNOPSIS
/usr/bin/savecore [-Lvd] [-f dumpfile] [directory]
DESCRIPTION
The savecore utility saves a crash dump of the kernel (assuming that one was made) and writes a reboot message in the shutdown log. It is
invoked by the dumpadm service each time the system boots.
savecore saves the crash dump data in the file directory/vmcore.n and the kernel's namelist in directory/unix.n. The trailing .n in the
pathnames is replaced by a number which grows every time savecore is run in that directory.
Before writing out a crash dump, savecore reads a number from the file directory/minfree. This is the minimum number of kilobytes that must
remain free on the file system containing directory. If after saving the crash dump the file system containing directory would have less
free space the number of kilobytes specified in minfree, the crash dump is not saved. if the minfree file does not exist, savecore assumes
a minfree value of 1 megabyte.
The savecore utility also logs a reboot message using facility LOG_AUTH (see syslog(3C)). If the system crashed as a result of a panic,
savecore logs the panic string too.
OPTIONS
The following options are supported:
-d Disregard dump header valid flag. Force savecore to attempt to save a crash dump even if the header information stored on
the dump device indicates the dump has already been saved.
-f dumpfile Attempt to save a crash dump from the specified file instead of from the system's current dump device. This option may be
useful if the information stored on the dump device has been copied to an on-disk file by means of the dd(1M) command.
-L Save a crash dump of the live running Solaris system, without actually rebooting or altering the system in any way. This
option forces savecore to save a live snapshot of the system to the dump device, and then immediately to retrieve the data
and to write it out to a new set of crash dump files in the specified directory. Live system crash dumps can only be per-
formed if you have configured your system to have a dedicated dump device using dumpadm(1M).
savecore -L does not suspend the system, so the contents of memory continue to change while the dump is saved. This means
that live crash dumps are not fully self-consistent.
-v Verbose. Enables verbose error messages from savecore.
OPERANDS
The following operands are supported:
directory Save the crash dump files to the specified directory. If directory is not specified, savecore saves the crash dump
files to the default savecore directory, configured by dumpadm(1M).
FILES
directory/vmcore.n
directory/unix.n
directory/bounds
directory/minfree
/var/crash/'uname -n' default crash dump directory
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
adb(1), mdb(1), svcs(1), dd(1M), dumpadm(1M), svcadm(1M), syslog(3C), attributes(5), smf(5)
NOTES
The system crash dump service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/dumpadm:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
If the dump device is also being used as a swap device, you must run savecore very soon after booting, before the swap space containing the
crash dump is overwritten by programs currently running.
SunOS 5.10 25 Sep 2004 savecore(1M)