From nobody Sat Jul 27 19:41:06 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WWZkB2xWYz5RYMx for ; Sat, 27 Jul 2024 19:41:22 +0000 (UTC) (envelope-from moonlapse81@gmail.com) Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WWZk94HMtz3xkP for ; Sat, 27 Jul 2024 19:41:21 +0000 (UTC) (envelope-from moonlapse81@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=h61YrTDk; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of moonlapse81@gmail.com designates 2607:f8b0:4864:20::d2e as permitted sender) smtp.mailfrom=moonlapse81@gmail.com Received: by mail-io1-xd2e.google.com with SMTP id ca18e2360f4ac-81f96eaa02aso40262139f.2 for ; Sat, 27 Jul 2024 12:41:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722109278; x=1722714078; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=dDVLe73uCi0n/3K3s4AYDxOkB6DleXLGUpdPkGjcbpw=; b=h61YrTDkdLubTuBrrdqJ6W/HPRHbUrTnNiar9U/CSWUEwN3Qyd43KR+kU6nsjdqIj9 eX+eXVqIUjs0TD8zjdNEKVHLIqZnVuWXZn5dIqn3wc9ClRYAnkHqEMazFLlJbrFReepL Fn677AO8wIIHSB1bVOK7dPD1POBOtnuYg/xeV0EnhZ6DP29eN65ArxZhHJpzDyZBi+Qg D0dy3iKZTqZu6Pm/TNAUwpANlej4rkG8q5b+/3VcovPZ1Khmu25Am2Aj6BGE6TOAVTCg boATFSG8eLad54UCQbK7LCldr6aAdXU/MflnO3NCz71KELZ9CoN13u64uuPFM8WuGvDS vRCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722109278; x=1722714078; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=dDVLe73uCi0n/3K3s4AYDxOkB6DleXLGUpdPkGjcbpw=; b=kzdKAIg+yeefpRKrC0k6JPOt9LInEc2blhZtzWUeVj11+xAXpb5Wk8Ei8dawMlDObG zGaGRjczKBoIf2yOkPUBqDwirgEfM0953oUzC/HK4gOuaY8Ajt2tFym4Fsx+pLr2jwx1 quXg84jB7c2rvh/OjFfdPlBqiaNmDvZWw3BG0xWecPb0JuuzoGFiQTzXy2lr1V/Svf+U Rb05YADW7M3EdoZpi8xojpI2mPGHrGdlgDQJli7kFtObOTtxpJQXaZucPGXB0uMpf0qu DaTyy6MOyDXjrVI2B64xAKBzoY8nLG2D+Xr0clQJanmbtLaMtu+Sj1wYMqNh+enSCSEX kTHw== X-Gm-Message-State: AOJu0YyPBf+R/MVJyvqrsAqaM5nHD4fdlQAUWJQkf2S9OjNTZ/BEkXLv aDeliwDOLtHpof+AYE7GC3E6mkO5326AYATSbrXECBHyfE/V8UjfLRmS6o8JoMZElz9ARTccEwc 8o6StXbowJNadm+e3RCYBbSPWLcwEiQ== X-Google-Smtp-Source: AGHT+IG/tDab+aXf2vQpKgMZU/rMVerq3NiQ8abNhBkVYXGzdjEMjN4jFrm0byTFI5ojVZ2DqixdifurQSwBSbG8e1Q= X-Received: by 2002:a05:6e02:1fcb:b0:375:8fa1:529a with SMTP id e9e14a558f8ab-39aec26da53mr36695615ab.10.1722109278215; Sat, 27 Jul 2024 12:41:18 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <20240727170122.675f6bfe@ernst.home> In-Reply-To: From: =?UTF-8?B?0J7Qu9C10LM=?= Date: Sat, 27 Jul 2024 19:41:06 +0000 Message-ID: Subject: Re: filemon To: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000cae780061e3fcfd7" X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_HAS_DN(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::d2e:from] X-Rspamd-Queue-Id: 4WWZk94HMtz3xkP --000000000000cae780061e3fcfd7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable slightly tangent question but does filemon and consequently WITH_META_MODE=3DYES work, when /usr/obj is on tmpfs? In my test, it is not and i tested without reboot, so /usr/obj is not removed. Reason is to avoid disk use when building world/kernel. On Sat, Jul 27, 2024 at 6:35=E2=80=AFPM void 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. > > man 4 filemon has the following > > NAME > filemon =E2=80=93 the filemon device > > [...] > > DESCRIPTION > The filemon device allows a process to collect file operations data > of > its children. The device /dev/filemon responds to two ioctl(2) > calls. > > [...] > > Are you sure it's not a device? The man page suggests otherwise. > > -- > > --000000000000cae780061e3fcfd7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
slightly tangent question but does filemon and conseq= uently WITH_META_MODE=3DYES work, when /usr/obj is on tmpfs? In my test, it= is not and i tested without reboot, so /usr/obj is not removed. Reason is = to avoid disk use when building world/kernel.

On Sat, J= ul 27, 2024 at 6:35=E2=80=AFPM 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.=C2=A0 So you can't hav= e "device
>filemon" in your kernel config file.

man 4 filemon has the following

NAME
=C2=A0 =C2=A0 =C2=A0 filemon =E2=80=93 the filemon device

[...]

DESCRIPTION
=C2=A0 =C2=A0 =C2=A0 The filemon device allows a process to collect file op= erations data of
=C2=A0 =C2=A0 =C2=A0 its children.=C2=A0 The device /dev/filemon responds t= o two ioctl(2) calls.

[...]

Are you sure it's not a device? The man page suggests otherwise.

--

--000000000000cae780061e3fcfd7--