From nobody Tue Nov 22 15:44:45 2022 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 UTF8SMTP id 4NGpVQ49kgz4hwKg for ; Tue, 22 Nov 2022 15:45:02 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with UTF8SMTPS id 4NGpVQ1WRHz4PXW for ; Tue, 22 Nov 2022 15:45:02 +0000 (UTC) (envelope-from kabaev@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qt1-x82f.google.com with SMTP id e15so9509900qts.1 for ; Tue, 22 Nov 2022 07:45:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:message-id:subject:cc:to:from :date:from:to:cc:subject:date:message-id:reply-to; bh=P2IAOuXlPBZcumTrRySEhC3kjiOYeB0s4Rn6nHeF4F0=; b=mf2jpCNf7apsEyNPVXo3OVc63N8R5YTnrtWVzYcNJW8/WheWuVmY8qOA4pPuPd/2k3 TAGyYLEaFCT9AmAjSoVo8fTPyUViaAG+PoOrJX2haszVLCWEc8nJgWwbMi12oeNBZhXu zVvVVT/jF7Su8X3DJ4n/zmihKs2kOopRGcHgweLkVoFpWh86ve1qN/aN9yunvggDlIve aTYeGfWg+hKgT9PURMsJLtOWWBzMUO80TvgzXLpDBEzjdvgHUu3UH3g+zaitvsNvqycC vFv0fCtG+RnNUAWGOf+6ASbzabmv0WtpQ+MZlfL2GGnC79vrSSJRxg7gjACMf/8R5vdd iVuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:references:in-reply-to:message-id:subject:cc:to:from :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=P2IAOuXlPBZcumTrRySEhC3kjiOYeB0s4Rn6nHeF4F0=; b=1xML3i7xB9c41zeEyhi1Fzm4NWRSOPU1+1JrHKbgn9s5x15iiMG910aKSckDmfd9Vw +TqLux3vEjkngQeBh9HzGPn5fOBXIyHSdcWrG4IdnQBE4/wgITdfe9vYpmG/piwxVCEP zq3dkbwXHoNO0XwqdcYAEwuHuqcod8NWYiU/b4JOqcowcPaA9toibQyLnNVMcjJdiC3D 2MZOFHu0EVVpAEy2/1KRdKyoFgd6tKk+9bjOjVruQbjJldMcxOkWw2/Rf1SHu/C/v9XE /mKAOBzZ1RuIcwAI4G+CVzyEGSW398TyXT+Lz+as4dsJQBScSToe1vHViU726t6QTB6f 7J1w== X-Gm-Message-State: ANoB5pkTOqqv+GY9Zjm9/txr7p7wKY67UuyoHSdeINUetN/UvvU/+zGn hncC08bxt+5qm+LOfeb+7kCNWGjHTkw= X-Google-Smtp-Source: AA0mqf5zswxOCr5xXKUneCROKwau3y2kdYfwtAa9EXAyt++/+RGpuuaQby/sUs3S9bHoEkOILf1Lhg== X-Received: by 2002:ac8:514b:0:b0:35d:5a2e:72f with SMTP id h11-20020ac8514b000000b0035d5a2e072fmr4355504qtn.324.1669131900844; Tue, 22 Nov 2022 07:45:00 -0800 (PST) Received: from kan ([2601:18f:701:29c0:2e4d:54ff:fe51:fcf3]) by smtp.gmail.com with ESMTPSA id j12-20020a05620a410c00b006eef13ef4c8sm10678559qko.94.2022.11.22.07.44.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Nov 2022 07:44:59 -0800 (PST) Date: Tue, 22 Nov 2022 10:44:45 -0500 From: Alexander Kabaev To: Dan Mack Cc: freebsd-current@freebsd.org Subject: Re: dmesg content lifetime Message-ID: <20221122104445.4ed88f6f@kan> In-Reply-To: <9d519f-ce87-72d-dc6-789817468974@macktronics.com> References: <9d519f-ce87-72d-dc6-789817468974@macktronics.com> X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: multipart/signed; boundary="Sig_/ImeeSaRkAnPSQSX=1cHYX=o"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Rspamd-Queue-Id: 4NGpVQ1WRHz4PXW X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --Sig_/ImeeSaRkAnPSQSX=1cHYX=o Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 22 Nov 2022 09:12:28 -0600 (CST) Dan Mack wrote: > It seems like dmesg content ages out over time. Is there a way to > leave the contents based on a fixed memory size instead? >=20 > Dan >=20 I think this is how it works: the kernel message bugger is of fixed size and kernel and syslog sequences (dmesg -a) share it. The other syslog users eventually puts enough content in there to displace all of kernel messages. If the kernel stays quiet, 'dmesg' then returns nothing, as by default it filters syslog entries that do not KERN facility out, see sbin/dmesg/dmesg.c. --=20 Alexander Kabaev --Sig_/ImeeSaRkAnPSQSX=1cHYX=o Content-Type: application/pgp-signature Content-Description: Цифровая подпись OpenPGP -----BEGIN PGP SIGNATURE----- iL0EARECAH0WIQR0dKhH2/VQpfw+8iNDrPWMyb5dlgUCY3zubl8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0NzQ3 NEE4NDdEQkY1NTBBNUZDM0VGMjIzNDNBQ0Y1OENDOUJFNUQ5NgAKCRBDrPWMyb5d lpWbAKDQjgJPdILO4zm/hhcHUxb+TH46VwCfTexeYDaj7/ire5gpCGz4LeTvKZc= =6xPU -----END PGP SIGNATURE----- --Sig_/ImeeSaRkAnPSQSX=1cHYX=o--