#24158: I get this error "Looks like our kernel doesn't have the support for
KIST
anymore." on my relay
---------------------------+------------------------------------
Reporter: Dbryrtfbcbhgf | Owner: (none)
Type: defect | Status: needs_information
Priority: Medium | Milestone: Tor: 0.3.2.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-sched | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
---------------------------+------------------------------------
Comment (by pastly):
Replying to [comment:6 dgoulet]:
> I think that notice will be logged each time the conf changed or new
consensus while having KIST disabled by no kernel support. We should
probably log it once and only once.
>{{{
>log_notice(LD_SCHED, "Scheduler type KIST has been disabled by "
> "the consensus or no kernel support.");
>}}}
I'm skimmed the code a bit and I think you're right. Every consensus we
probably log the above message, but only on the first consensus after
having to fall back do we log `Scheduler type KISTLite has been enabled.`
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24158#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
