diff options
Diffstat (limited to 'share/man/man9/shutdownhook_establish.9')
| -rw-r--r-- | share/man/man9/shutdownhook_establish.9 | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/share/man/man9/shutdownhook_establish.9 b/share/man/man9/shutdownhook_establish.9 index 7ebbd3f4a20..a23ce8bbd34 100644 --- a/share/man/man9/shutdownhook_establish.9 +++ b/share/man/man9/shutdownhook_establish.9 @@ -1,4 +1,4 @@ -.\" $OpenBSD: shutdownhook_establish.9,v 1.12 2003/03/10 19:56:29 tedu Exp $ +.\" $OpenBSD: shutdownhook_establish.9,v 1.13 2003/06/06 20:56:32 jmc Exp $ .\" $NetBSD: shutdownhook_establish.9,v 1.1 1995/11/25 21:24:52 perry Exp $ .\" .\" Copyright (c) 1994 Christopher G. Demetriou @@ -77,19 +77,6 @@ integrity (because the system could be rebooting after a crash). Shutdown hooks are, like startup hooks, implemented via the more general .Xr dohooks 9 API. -.Sh CAVEATS -Shutdown hooks should only be used to do what's strictly necessary -to do to ensure a correct reboot. -Since shutdown hooks are run even after a panic, a panic caused by a -shutdown hook will automatically cause the shutdown hook to be run again -causing an endless loop. -An example of things that need to be done in a shutdown hook could be -stopping DMA engines that might corrupt memory when rebooting. -An example of things that shouldn't be done in a shutdown hook is syncing -the file systems. -Once again, since the system could be rebooting because of an internal -inconsistency, writing down anything to permanent storage or trusting -the internal state of the system is a very bad idea. .Sh RETURN VALUES If successful, .Fn shutdownhook_establish @@ -110,5 +97,18 @@ is no longer running. .Xr dohooks 9 , .Xr doshutdownhooks 9 , .Xr dostartuphooks 9 +.Sh CAVEATS +Shutdown hooks should only be used to do what's strictly necessary +to do to ensure a correct reboot. +Since shutdown hooks are run even after a panic, a panic caused by a +shutdown hook will automatically cause the shutdown hook to be run again +causing an endless loop. +An example of things that need to be done in a shutdown hook could be +stopping DMA engines that might corrupt memory when rebooting. +An example of things that shouldn't be done in a shutdown hook is syncing +the file systems. +Once again, since the system could be rebooting because of an internal +inconsistency, writing down anything to permanent storage or trusting +the internal state of the system is a very bad idea. .Sh BUGS The names are clumsy, at best. |