summaryrefslogtreecommitdiffstats
path: root/usr.bin/netstat/unix.c
diff options
context:
space:
mode:
authorhenning <henning@openbsd.org>2015-02-12 01:24:10 +0000
committerhenning <henning@openbsd.org>2015-02-12 01:24:10 +0000
commitf61b1efccea797fa6960a16e5c6490f40a6ff5a0 (patch)
tree001158c850b148370f8f58e53ccf3815faefbde5 /usr.bin/netstat/unix.c
parentber_printf_elements should return NULL if any of its parts fail. (diff)
downloadwireguard-openbsd-f61b1efccea797fa6960a16e5c6490f40a6ff5a0.tar.xz
wireguard-openbsd-f61b1efccea797fa6960a16e5c6490f40a6ff5a0.zip
change log(matches) semantics slightly to make it more useful. since it
is a debug tool change of semantics not considered problematic. up until now, log(matches) forced logging on subsequent matching rules, the actual logging used the log settings from that matched rule. now, log(matches) causes subsequent matches to be logged with the log settings from the log(matches) rule. in particular (this was the driving point), log(matches, to pflog23) allows you to have the trace log going to a seperate pflog interface, not clobbering your regular pflogs, actually not affecting them at all. long conversation with bluhm about it, which didn't lead to a single bit changed in the diff but was very very helpful. ok bluhm as well.
Diffstat (limited to 'usr.bin/netstat/unix.c')
0 files changed, 0 insertions, 0 deletions