From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4dxn2L3Bwlz332Z for ; Thu, 22 Jan 2026 16:43:54 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4dxn2G5g6tz2xdr for ; Thu, 22 Jan 2026 16:43:50 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4dxn2F2Br3z1qS; Thu, 22 Jan 2026 16:43:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769100229; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=eaKyDPHF3fXMapaJoHGhljZrSuJvGfeP4b8w7qlyXQw=; b=fDXylIOd/zaEq56cmYMVf0RpfsWnNrH2Fu1s398QE9kjOnQZD5bGmoUsO/7FJAFRCGKZIu OiWT4qKuwl699hscEti8/+LvW83O1kamvt+962xqJjSZQ1l/EApDHuzThg4VfJI3rT+1MO 33g69kglTg1yDFT+fWiddEBeLwqUDl2E4DPm5aEdCZGExf3OPTbxPggcLdLh6zPBWWR3F1 z4L3hZuvoLnYn+Vi7VzNoK/IzHZjtdK+K3rR72nj6ga6byhSB6Ieh3Q/IsYkkT2za2CD2p VhU6pW6LVfkzt/92mKQPvOi7KAeezWsRdhd6Y1YwwCSJH4LNk4X1UFwI67zKeQ== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769100229; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=eaKyDPHF3fXMapaJoHGhljZrSuJvGfeP4b8w7qlyXQw=; b=aBHpf3WHvpuHShKLEkbsiwITzvYfDSJH1n6sQWli0A1Rhjg/8/5hoNOdE00OQpyriGbMem LVZvsAc6qQorMoAw== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Core 199 - collectd - cpufreq-plugin floods syslog From: Michael Tremer In-Reply-To: <5b78cf81-b059-43ef-ab33-038ca1579f22@ipfire.org> Date: Thu, 22 Jan 2026 16:43:48 +0000 Cc: Tom Rymes , "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: References: <5b78cf81-b059-43ef-ab33-038ca1579f22@ipfire.org> To: Matthias Fischer Hello Matthias, I think too that your emails are making it to the list just fine. The = archive got them too: = https://lists.ipfire.org/development/7cf06956-d5b8-4769-b020-144737f1da10@= ipfire.org/T/#m01f734b0ade53d5f047771ea7cae1c22347b82ad Since we changed to mlmmj you won=E2=80=99t receive a copy from the list = again. Mailman could be configured to send you a copy if your own mail, = but since you normally don=E2=80=99t get that when you send a personal = email, why would you get that from a list? Just assume your email made = it. If you get them double, this is probably because people are replying to = you as well as the list. Like I am doing now. Your email client should = be able to deduplicate emails by their ID. Mine would never show the = same email twice. Which one are you using? I would like us all to have a high confidence in this email system = working, so if you see any problems, please let me know. All the best, -Michael > On 22 Jan 2026, at 06:32, Matthias Fischer = wrote: >=20 > On 22.01.2026 01:49, Tom Rymes wrote: >> Matthias, >=20 > Hi Tom, >=20 >> I always get your emails to the list, followed by a second message = that your emails aren=E2=80=99t appearing on the list. I=E2=80=99m = guessing the issue is that you are not receiving a copy of your own = e-mails? >=20 > Exactly. >=20 > This started "some day" - so that I couldn't tell if my mail came = through. >=20 > On the other hand, I receive mails like yours always *twice*. Funny. = One > of these mails comes with a List-ID from = . > Its a bit weird... >=20 >> Either way, it always seems to be working properly to me. >=20 > Ok - I think, for the moment I can live with that... ;-) >=20 > Best > Matthias >=20 >>=20 >> Tom >>=20 >>> On Jan 21, 2026, at 5:52 PM, Matthias Fischer = wrote: >>>=20 >>> 2cd try: >>> For reasons unknown to me, my Mails no longer appear on the list, = even >>> though I can send them there without any errors. >>>=20 >>> Therefore: next attempt - plus CC to MT [Hi Michael... ;-) ] >>>=20 >>> ----------------- >>>=20 >>> Hi, >>>=20 >>> just in case that this happens to somebody else: >>>=20 >>> Some days ago I made a fresh install of Core 199 with a new machine = and >>> rather old cpu (i7-2700). Runs fine and has more power than the old = Duo >>> box. Fits my needs. >>>=20 >>> But I couldn't disable HT in BIOS - 'htop' finds eight CPUs. Should = be >>> no problem - but it is. >>>=20 >>> The problem came with the 'cpufreq'-plugin, my logs were flooded = with >>> warnings: >>> "cpufreq plugin: Reading >>> "/sys/devices/system/cpu/cpu4[5,6,7]/cpufreq/scaling_cur_freq" = failed." >>>=20 >>> Because of the deactivation, 'scaling_cur_freq' was empty, there = were >>> complains about CPU 4-7 (the deactivated ones) and in no time my log = was >>> filled with about 10000 'collectd'-entries. >>>=20 >>> My solution was to change the loglevel of the 'Plugin syslog' in >>> 'collectd.conf' from 'info' to 'err'. >>>=20 >>> Can anyone confirm this behaviour? >>>=20 >>> Best >>> Matthias >>>=20 >>=20 >>=20 >=20 >=20