Date: Wed, 28 Jul 2021 21:34:02 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 257314] FBSD 13 crash after some KDE parts crash supposing out of swap space Message-ID: <bug-257314-227-pItCXY1KfE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257314-227@https.bugs.freebsd.org/bugzilla/> References: <bug-257314-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257314 --- Comment #39 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Graham Perrin from comment #38) # sysctl -T vfs.zfs.arc.min vfs.zfs.arc.min: 0 Note: -T Display only variables that are settable via loader (CTLFLAG_TUN). # sysctl -W vfs.zfs.arc.min vfs.zfs.arc.min: 0 Note: -W Display only writable variables that are not statistical= .=20 Useful for determining the set of runtime tunable sysctls. So vfs.zfs.arc.min looks to be both a load-time tunable (-T) and a later writeable variable (-W). To illustrate what happens for -T and -W output when the name is loader-tunable but not later a writable variable (as an example): # sysctl -W kern.maxproc # sysctl -T kern.maxproc kern.maxproc: 70308 I'll note that I also see the 0 value for vfs.zfs.arc.min but I do no tuning of ZFS (I use defaults) and the system used for the above commands has 64 GiByte of RAM. My usage context is very different from chrome/gimp/plasmashell/Xorg and so my lack of seeing OOM activity does not mean much for the bugzilla report. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257314-227-pItCXY1KfE>