lkml.org 
[lkml]   [2001]   [Sep]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: reboot notifier priority definitions
> 
> I think this misses the point of reboot notifiers (as I understand
> it).
>
> There are *only* meant for "physical" sorts of things.
> The comment in the code says:
> * Notifier list for kernel code which wants to be called
> * at shutdown. This is used to stop any idling DMA operations
> * and the like.
>
> md, lvm, knfsd and tux have no business registering a reboot notifier.
> If they have something to shut down, it should be shut down in a
> higher-level way, such as when a process gets a signal.
>
Even then: My servers do have watchdog cards. Unfortunately without the
priority definitions the watchdog card was shut down prior to the oops. Thus,
due to missing priority, the system did require hitting the reboot button.
So some well defined priorization is still required.


Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:03    [W:0.049 / U:3.344 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site