#23581: Die more helpfully if Schedulers option isn't compatible with platform --------------------------+------------------------------------ Reporter: pastly | Owner: (none) Type: defect | Status: new 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 dgoulet): I see two possible behaviors to solve this: 1. We exit(1) if `select_scheduler()` can't set a scheduler. So in this case, you tried to put KIST only on a platform that doesn't support it, we stop and ask you to fix your torrc. 2. We fallback to some default (`KISTLite` for instance) and warn the user. The approach in (1) has a bad side effect of if at runtime the new type is not usable well tor will just stop... As for (2), it is very possible the user just don't notice the fallback and end up with a tor scheduler it didn't want (not sure that's really a big issue...) For now, I'm for (2) ? Objections? -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23581#comment:2> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs