Re: crash: savecore - saves core dump every day?
2006/3/10, Nick Holland [EMAIL PROTECTED]: I'm not entirely sure I understand your question, the subject and the body of your message don't seem to be completely related. However, I think you may find the answers to your questions in man 8 crash Third paragraph (more or less, depending what one counts) tells what conditions cause the in-RAM image to be written to disk in the swap partition. If that happens, an attempt will be made to dump it to physical disk upon reboot. Will try to ask more clearly: How does savecore work in sense of detecting that condition to save core dump to swap space has been accomplished? Does it get message from kernel (which IPC technique?) or does it something like polling for special event (eg. newly created file)? regards
fdisk / signature: 0xAA55
Hi, when installing OpenBSD fdisk utility does extra show selected disk's MBR signature 0xAA55. Why does it do? Do more MBR signatures exist? Or is this only for verification of disk's mbr health? greetings
Re: fdisk / signature: 0xAA55
2006/3/9, Paul de Weerd [EMAIL PROTECTED]: This signature is represented (in binary) as 0b1010101001010101. The alternating bit pattern was thought to be a protection against certain failures (drive or controller). Of course, this is an i386ism (also present on amd64 I believe). Lots of other architectures may take different approaches. Nice explanation, thank you!
crash: savecore - saves core dump every day?
Hi, from the faq: Upon reboot, savecore(8)will attempt to save the contents of the swap partition to a file in /var/crash savecore would be called by /etc/rc. So which criterias must be fulfilled to make core dump upon reboot? Does savecore look for special file names at special places? Who makes the rule? greetings
