From nobody Thu May 20 18:59:17 2021 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 E933C621B7B for ; Thu, 20 May 2021 18:59:19 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FmJtv5F98z4RtJ; Thu, 20 May 2021 18:59:19 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id 14KIxHU6087646 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 20 May 2021 11:59:17 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id 14KIxHRH087645; Thu, 20 May 2021 11:59:17 -0700 (PDT) (envelope-from jmg) Date: Thu, 20 May 2021 11:59:17 -0700 From: John-Mark Gurney To: Michael Gmelin Cc: "freebsd-current@freebsd.org" , cem@FreeBSD.org Subject: Re: Reducing SIGINFO verbosity Message-ID: <20210520185917.GL14975@funkthat.com> Mail-Followup-To: Michael Gmelin , "freebsd-current@freebsd.org" , cem@FreeBSD.org References: <20210520180155.3e23500e@bsd64.grem.de> 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: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210520180155.3e23500e@bsd64.grem.de> X-Operating-System: FreeBSD 11.3-STABLE amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Thu, 20 May 2021 11:59:17 -0700 (PDT) X-Rspamd-Queue-Id: 4FmJtv5F98z4RtJ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Michael Gmelin wrote this message on Thu, May 20, 2021 at 18:01 +0200: > I'm leaving this here, mostly so that others (or future me) can google > it up. > > Traditionally, CTRL-t would give a one-line output + whatever the > process specific signal handler comes up with: > > # sleep 120 <--- hits CTRL-t > load: 0.27 cmd: sleep 38162 [nanslp] 0.64r 0.00u 0.00s 0% 1780k > sleep: about 119 second(s) left out of the original 120 > > # cat <--- hits CTRL-t > load: 0.02 cmd: cat 24379 [ttyin] 0.63r 0.00u 0.00s 0% 2308k > > > On 13 I get: > > # sleep 120 <--- hits CTRL-t > load: 0.12 cmd: sleep 3241 [nanslp] 0.52r 0.00u 0.00s 0% 2172k > mi_switch+0xc1 sleepq_catch_signals+0x2e6 sleepq_timedwait_sig+0x12 > _sleep+0x199 kern_clock_nanosleep+0x1e1 sys_nanosleep+0x3b > amd64_syscall+0x10c fast_syscall_common+0xf8 sleep: about 119 > second(s) left out of the original 120 > > # cat <--- hits CTRL-t > load: 0.09 cmd: cat 3240 [ttyin] 0.23r 0.00u 0.00s 0% 2300k > mi_switch+0xc1 sleepq_catch_signals+0x2e6 sleepq_wait_sig+0x9 > _cv_wait_sig+0xe4 tty_wait+0x1c ttydisc_read+0x2ac ttydev_read+0x56 > devfs_read_f+0xd5 dofileread+0x81 sys_read+0xbc amd64_syscall+0x10c > fast_syscall_common+0xf8 > > which is quite way too verbose when checking the progress of > long-running processes, like cp, dd, or poudriere. Especially as CTRL-t > is part of the user experience to me - I use it to interact with the > machine outside of debugging software issues. > > Setting > > sysctl kern.tty_info_kstacks=0 > echo kern.tty_info_kstacks=0 >>/etc/sysctl.conf > > fixes this permanently. > > Apparently, this was enabled by default on purpose[0], so that people > find the feature (which certainly worked ^_^), but I think it would > been worth mentioning the sysctl somewhere in the release notes/errata, > so that people understand how to disable it again. I think the original intent was to disable this on -stable or at least -RELEASEs, but it looks like this didn't happen. This is VERY helpful for a developer, but not as helpful for most users. Conrad, Should this be disabled on -stable now? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."