Date: Sun, 28 Jul 2024 08:32:48 +0000 From: Gary Jennejohn <garyj@gmx.de> To: freebsd-current@freebsd.org Subject: Re: filemon Message-ID: <20240728103248.4266cd7e@ernst.home> In-Reply-To: <ZqU9Cd70-21EPx_L@int21h> References: <ZqT6_a_0F8DCUsBm@int21h> <CAFDf7UKxhSu%2BqMGV1KahrSX9ho8vFut4avxNVX4D8QGa6%2B%2BTjQ@mail.gmail.com> <20240727170122.675f6bfe@ernst.home> <ZqU9Cd70-21EPx_L@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 27 Jul 2024 19:31:37 +0100 void <void@f-m.fm> wrote: > On Sat, Jul 27, 2024 at 03:01:22PM +0000, Gary Jennejohn wrote: > > >filemon is not a device, it's an option. So you can't have "device > >filemon" in your kernel config file. > > > >I compile it with makeoptions MODULES_OVERRIDE=3D"filemon ..." in my > >kernel config file. > > What's the actual line in your kernel config file please? > makeoptions MODULES_OVERRIDE=3D"cpuctl filemon aesni vesa amdsmn amdte= mp" These are the only modules under /usr/src which I use, so I limit building modules using MODULES_OVERRIDE. > >I also load it from /boot/loader.conf using filemon_load=3D"YES" > > Why do you do both? (I presume both as you're saying you 'also load') > Because filemon.ko has to be loaded. But you're right, device filemon works in my kernel config file. I added device filemon (and removed it from MODULES_OVERRIDE) and my kernel compiled successfully. I removed filemon_load=3D"YES" from /boot/loader.conf and booted the new kernel. kldstat -v showed that filemon was in the kernel. So I guess I misunderstood what optional means in /sys/conf/files:dev/filemon/filemon.c optional filemon =2D- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240728103248.4266cd7e>