Date: Tue, 30 Jul 2024 11:10:06 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: Gary Jennejohn <garyj@gmx.de> Cc: freebsd-current@freebsd.org Subject: Re: filemon Message-ID: <865xsn6ya9.fsf@ltc.des.dev> In-Reply-To: <20240727170122.675f6bfe@ernst.home> (Gary Jennejohn's message of "Sat, 27 Jul 2024 15:01:22 %2B0000") References: <ZqT6_a_0F8DCUsBm@int21h> <CAFDf7UKxhSu%2BqMGV1KahrSX9ho8vFut4avxNVX4D8QGa6%2B%2BTjQ@mail.gmail.com> <20240727170122.675f6bfe@ernst.home>
index | next in thread | previous in thread | raw e-mail
Gary Jennejohn <garyj@gmx.de> writes:
> filemon is not a device, it's an option. So you can't have "device
> filemon" in your kernel config file.
There is very little difference between options and devices in kernel
configuration files, but for what it's worth, filemon is a device, not
an option.
> I compile it with makeoptions MODULES_OVERRIDE="filemon ..." in my
> kernel config file.
All that does is build the module as part of the buildkernel process.
It does not include the module in the kernel, nor does it cause the
module to be loaded at boot time.
> I also load it from /boot/loader.conf using filemon_load="YES"
This does cause the module to be loaded at boot time, but it's slower
than loading it later, and it increases memory fragmentation. A better
option is to include "filemon" in the kld_list variable in /etc/rc.conf
or /etc/rc.conf.d/kld. For instance,
% cat /etc/rc.conf.d/kld/filemon
kld_list="${kld_list} filemon"
DES
--
Dag-Erling Smørgrav - des@FreeBSD.org
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?865xsn6ya9.fsf>