The author mentioned bugs that are more likely to occur sooner rather than later, such as startup bugs (errors in the boot code or kernel initialization). One

The author mentioned bugs that are more likely to occur sooner rather than later, such as startup bugs (errors in the boot code or kernel initialization). One can also get shutdown bugs. If you like to brag about how long your server stays up, you'll never see them, but if you shut down your box at the end of your workday, you're likely to. I myself isolated a bug in the Classic Mac OS 7.5.2 (or maybe it was 7.5.3) Open Transport Ethernet shutdown procedure. The way I found the bug was to write an AppleScript that consisted of "Tell Finder Restart", then placed that in the Startup Items folder. I very quickly found that the bug occurred on networked computers, but not on those which were not connected. For *NIX you could test the kernel's startup and shutdown by having an init script that did "shutdown -r now". I don't ever hear about others testing this way. I didn't invent this, it was used by another department in my same building to test development builds of System 7. They had a couple hundred Macs many of them would do nothing but reboot 24/7.