Gustavo Iñiguez Goia 785500cd08 clean dns ebpf hooks on exit ... We were not reacting to common exit signals, only to kill/interrupt signals, so the DNS uprobes were never properly removed. Each uprobe has the PID of the daemon in the identifier, so in theory, there shouldn't be conflicts, but better clean our probes on exit. previous to this commit with the daemon running (and lot of starts/stops): ~ # cat /sys/kernel/debug/tracing/uprobe_events |wc -l 367 after stopping the daemon: ~ # cat /sys/kernel/debug/tracing/uprobe_events |wc -l 364 ~ # > /sys/kernel/debug/tracing/uprobe_events ~ # cat /sys/kernel/debug/tracing/uprobe_events |wc -l 0 ~ # cp opensnitchd-new /usr/bin/opensnitchd ; service opensnitchd start ~ # cat /sys/kernel/debug/tracing/uprobe_events |wc -l 3 ~ # service opensnitchd stop ~ # cat /sys/kernel/debug/tracing/uprobe_events |wc -l 0		2024-01-28 01:10:00 +01:00
..
systemd	structs fields reorganized	2024-01-14 20:44:49 +01:00
ebpfhook.go	clean dns ebpf hooks on exit	2024-01-28 01:10:00 +01:00
parse.go	updated import paths	2020-12-09 18:18:42 +01:00
track.go	dns/logs minor improvements	2023-03-10 21:30:28 +01:00