[src/trunk]: src/usr.sbin/npf/npfctl one more fixed

[christos <christos%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/6978d40f8027
branches:  trunk
changeset: 785390:6978d40f8027
user:      christos <christos%NetBSD.org@localhost>
date:      Mon Mar 11 16:38:31 2013 +0000

description:
one more fixed

diffstat:

 usr.sbin/npf/npfctl/todo |  3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diffs (17 lines):

diff -r 8214fe065198 -r 6978d40f8027 usr.sbin/npf/npfctl/todo
--- a/usr.sbin/npf/npfctl/todo  Mon Mar 11 16:37:43 2013 +0000
+++ b/usr.sbin/npf/npfctl/todo  Mon Mar 11 16:38:31 2013 +0000
@@ -15,7 +15,6 @@
    for system failures is probably not good enough. For example if a module
    failed to autoload, it is probably an error and it should be reported
    differently?
--- fix 'ifconfig npflog0 destroy; modunload if_npflog'
 
 ok npf and dependent modules should autoload automagically as they are used
 ok have a way to register cloners? through a mapping file? consistently naming
@@ -31,3 +30,5 @@
 ok get better messages from the kernel when things fail: Ok with
    DEBUG/DIAGNOSTIC, you get the file/line in the kernel that failed 
    which is good enough.
+ok 'ifconfig npflog0 destroy; modunload if_npflog'. Remove dependency
+   on npf_ext_log module, since if_npflog can load and unload independently.