anchors enable / disable

2021-12-17 Thread Holger Glaess
hi is there an possibility  to enable / disable anchors with pfctl ? like pfctl -aFooBar -T enable Feature Request ? Holger

Re: Profiling ifconfig

2021-12-17 Thread Vladimir Nikishkin
Profiling ifconfig was my first guess, I am not an experienced programmer in any sense of the word. I did the ktrace/kdump run, and the result is just 65 lines, most of which seem normal (attached). The suspicious lines below: ``` 78429 ifconfig 1639744429.761912 CALL socket(AF_INET,0x2,0) 7842

Re: anchors enable / disable

2021-12-17 Thread beebeetles
Sounds like the feature is already there, in a different way. Enable: pfctl -aFooBar -f PathToFooBar Disable: pfctl -aFooBar -F all Regards. On 12/17/21 07:34, Holger Glaess wrote: hi is there an possibility  to enable / disable anchors with pfctl ? like pfctl -aFooBar -T enable Feat

unknown warning option '-Wno-unused-but-set-variable'

2021-12-17 Thread Jan Stary
This is current/i386 on an ALIX.1E (dmesg below). The kernel does not build with the current cvs: cat /usr/src/sys/arch/i386/i386/genassym.cf /usr/src/sys/arch/i386/i386/genassym.cf | sh /usr/src/sys/kern/genassym.sh cc -no-integrated-as -g -Werror -Wall -Wimplicit-function-declaration -Wno-p

Re: unknown warning option '-Wno-unused-but-set-variable'

2021-12-17 Thread Patrick Wildt
Kernel Makefiles were adjusted to compile with clang 13. Either take out the warnings so you can compile with old-clang, or rebuild clang. What should have been done was to add no-op arguments for these warnings into clang 11 to ease the transition to clang 13, but somehow no one did it, huh. Pa

update groups (please)

2021-12-17 Thread Gábor Légrádi
0 C Hungary T Budapest F Irregular O Magyar BSD Egyesület (Hungarian BSD Association) I Gábor Légrádi M i...@bsd.hu U http://bsd.hu N *BSD. -- "Share what you know. Learn what you don't."

"run0: missing endpoint" on OpenBSD 7.0

2021-12-17 Thread Jeff Ross
Hi all, Trying to replace an rsu usb wifi adapter with one that is a little more resilient because the rsu locks up about 4 or 5 times a day and it takes a reboot to get it to come back. Full dmesg follows but on both this amd64 computer and a rpi 3B+ the result is the same: run0 at uhub0

Re: "run0: missing endpoint" on OpenBSD 7.0

2021-12-17 Thread Stefan Sperling
On Fri, Dec 17, 2021 at 02:14:31PM -0700, Jeff Ross wrote: > Hi all, > > Trying to replace an rsu usb wifi adapter with one that is a little more > resilient because the rsu locks up about 4 or 5 times a day and it takes a > reboot to get it to come back. > > Full dmesg follows but on both this a

Re: "run0: missing endpoint" on OpenBSD 7.0

2021-12-17 Thread Jeff Ross
On 12/17/21 4:03 PM, Stefan Sperling wrote: On Fri, Dec 17, 2021 at 02:14:31PM -0700, Jeff Ross wrote: Hi all, Trying to replace an rsu usb wifi adapter with one that is a little more resilient because the rsu locks up about 4 or 5 times a day and it takes a reboot to get it to come back. Full

suspend/resume kills X

2021-12-17 Thread Jan Stary
This is current/amd64 on a PC (dmesg below). After boot, I log into X, running cwm, an xterm, and a script(1) of this. |-+= 14944 root /usr/X11R6/bin/xenodm | |-+= 56178 _x11 /usr/X11R6/bin/X :0 vt05 -auth /etc/X11/xenodm/authdir/authf | | \--- 57333 root X: [priv] (Xorg) | \-+= 91925 root xe