summaryrefslogtreecommitdiffstats
path: root/share/man/man4/netgraph.4
diff options
context:
space:
mode:
Diffstat (limited to 'share/man/man4/netgraph.4')
-rw-r--r--share/man/man4/netgraph.48
1 files changed, 4 insertions, 4 deletions
diff --git a/share/man/man4/netgraph.4 b/share/man/man4/netgraph.4
index ad992e0..e62e29e 100644
--- a/share/man/man4/netgraph.4
+++ b/share/man/man4/netgraph.4
@@ -433,14 +433,14 @@ Some nodes (usually associated with a piece of hardware) may be
in that a shutdown breaks all edges and resets the node,
but does not remove it.
In this case, the shutdown method should not
-free its resources, but rather, clean up and then clear the
-.Dv NG_INVALID
-flag to signal the generic code that the shutdown is aborted.
+free its resources, but rather, clean up and then call the
+.Em NG_NODE_REVIVE()
+macro to signal the generic code that the shutdown is aborted.
In the case where the shutdown is started by the node itself due to hardware
removal or unloading (via
.Fn ng_rmnode_self ) ,
it should set the
-.Dv NG_REALLY_DIE
+.Dv NGF_REALLY_DIE
flag to signal to its own shutdown method that it is not to persist.
.El
.Ss Sending and Receiving Data
OpenPOWER on IntegriCloud