Re: Reducing SIGINFO verbosity
- Reply: Warner Losh : "Re: Reducing SIGINFO verbosity"
- In reply to: Warner Losh : "Re: Reducing SIGINFO verbosity"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 18 Apr 2023 10:35:57 UTC
On Thu, 23 Jun 2022 11:15:55 -0600 Warner Losh <imp@bsdimp.com> wrote: > On Sun, Jun 19, 2022 at 6:06 AM Michael Gmelin <freebsd@grem.de> > wrote: > > > > > > > On Fri, 21 May 2021 08:36:49 -0600 > > Warner Losh <imp@bsdimp.com> wrote: > > > > > On Fri, May 21, 2021 at 7:38 AM Ceri Davies <ceri@submonkey.net> > > > wrote: > > > > > > > On Thu, May 20, 2021 at 03:57:17PM -0700, Conrad Meyer wrote: > > > > > No, I don’t think there’s any reason to default it > > > > > differently on stable > > > > vs > > > > > current. I think it’s useful (and I prefer the more verbose > > > > > form, which isn’t the default). > > > > > > > > I agree that there's no reason for the default to be different, > > > > but I would say that it is much easier for someone who knows > > > > that there is a default to be changed to change it, than it is > > > > for someone who does not. Therefore, if the information is not > > > > useful to someone who does not know how to get rid of it, then > > > > it should default to not being displayed, IMHO. > > > > > > > > > > I plan on changing the default for non-INVARIANT kernels back to > > > the old behavior. > > > > > > INVARIANT kernels will keep this behavior because it's a debugging > > > kernel and this is one more thing to help debugging problems. > > > > > > > Did this ever happen? I just installed a fresh 13.1-RELEASE > > production system (non-INVARIANT kernel) and it seems like SIGINFO > > still outputs kernel stack information. > > > > https://reviews.freebsd.org/D35576 for those who wish to weigh in. > > Warner > > Hi Warner, I just installed 13.2-RELEASE, seems like this was never MFCd (it is in main, but not in stable/13 or releng/13.2). TBH, I could've checked myself back then (it's so easy to forget to MFC). Cheers Michael p.s. Learned about it by hitting ctrl-t to check if freebsd-update on my slow test machine is actually alive :D -- Michael Gmelin