Re: Thinkpad Gets Very Hot
On 2023-11-07, luffy20201 wrote: > Hi, I've been an OpenBSD user for a year now, but I've never been able to > disable Acpitz. I have tried everything, and nothing has worked. I use a > Thinkpad X220, and it gets really hot. I need some help with this, can you > please guys lend a hand? Thank You It's an old machine. Make sure the fan is reasonably clean (don't do this by just blowing air through it - hold it in place so it doesn't spin too fast). You may need to renew the paste on the heatsink. Generally acpitz should not be disabled. -- Please keep replies on the mailing list.
Re: Thinkpad Gets Very Hot
Hello, luffy20...@protonmail.com (luffy20201), 2023.11.07 (Tue) 23:08 (CET): > Hi, I've been an OpenBSD user for a year now, but I've never been able > to disable Acpitz. I have tried everything, and nothing has worked. I details would be nice... why do you want to disable acpitz(4)? > use a Thinkpad X220, and it gets really hot. I need some help with > this, can you please guys lend a hand? Thank You Have you tried obsdfreqd? +++ $ pkg_info obsdfreqd Information for inst:obsdfreqd-1.2.0 Comment: userland daemon to manage CPU frequency Description: obsdfreqd is a CPU frequency scheduler daemon working in userland. It has many parameters to tweak the frequency like min/max frequency, polling frequency, inertia, step up/down size. obsdfreqd also support limiting the frequency upon reaching a given temperature to avoid a system spending time above the threshold. While it has many parameters, the defaults are good enough for everyone. Maintainer: Florian Viehweger WWW: https://git.sr.ht/~solene/obsdfreqd +++ I run it with the "-T 60" parameter, to make sure my notebook fans are inaudible. Marcus
Re: What happened to art4.html
crying won't bring them back cat wrote: > > for now > > It has been over a year > > On November 3, 2023 3:07:14 PM GMT, Christian Weisgerber > wrote: > >cat: > > > >> I tried to find OpenBSD's official branding art (not the release poster > >> art or anything) and I couldn't find it. Wikipedia attributes the logo svg > >> asset to http://www.openbsd.org/art4.html, but this page gives me a 404. I > >> can access it fine using archive.org and going to last year's archive, but > >> why is it not available now? > > > >If only changes were kept in a version control system that anybody > >could access... Oh, wait, they are! > > > >-- > >Changes by: t...@cvs.openbsd.org 2022/04/28 11:01:56 > > > >Removed files: > >. : art1.html art2.html art3.html art4.html > > > >Log message: > >almost all of the images on these pages give a 404 error since they're not > >stored in the www repo. remove them for now so people stop finding them on > >search engines. > >-- > > > >-- > >Christian "naddy" Weisgerber na...@mips.inka.de > >
Re: smtpd[68513]: warn: lost processor: spamassassin exited abnormally
On 2023/11/07 22:44:56 +0100, Giovanni Bechis wrote:
> On 11/7/23 20:16, Omar Polo wrote:
> > On 2023/11/07 19:30:43 +0100, Harald Dunkel wrote:
> >> Hi Omar,
> >>
> >> sorry for the delay, but I have good news: The patch seems to
> >> work. Of course I will continue to watch it.
> > Thanks for verifying!
> >
> > Before bumping the smtp-filter protocol version I took at look at what
> > we had in the port tree to know what would break, but this slipped.
> > apologize.
> >
> > If it's OK for Giovanni and Joerg I'd like to commit this and backport
> > to 7.4-stable (same diff tested by Harald, reattaching for convenience.)
> [...]
> > +Index: filter-spamassassin.go
> > +--- filter-spamassassin.go.orig
> > filter-spamassassin.go
> > +@@ -211,7 +211,7 @@ func run() {
> > + for in.Scan() {
> > + f := strings.Split(in.Text(), "|")
> > + t, ver, ev, sid := f[0], f[1], f[4], f[5]
> > +- if (t != "filter" && t != "report") || ver != "0.6" {
> > ++ if (t != "filter" && t != "report") || ver != "0.7" {
> > + l3.Err(fmt.Sprintln(sid, "protocol", t, ver))
> does this still works with previous protocol versions ?
The only difference between 0.6 and 0.7 is the order of the link-auth
fields (`result' and `username' were swapped.) As far as I can see,
filter-spamassassin doesn't use it, so it should work as usual on both
0.6 and 0.7 versions.
> ok giovanni@ in any case for current and 7.4 since it will be a no-op on
> OpenBSD.
Thanks :)
