diff options
| author | Nick Mathewson <nickm@torproject.org> | 2017-11-17 09:59:26 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2017-11-17 09:59:26 -0500 |
| commit | fcdec00685608c85161116bdb7408f33094ea3fa (patch) | |
| tree | 195124df1f483681f556630f58811bc67645cd7a /src/or/scheduler.c | |
| parent | 94dce246ee97884a546113827404a45d0f16c648 (diff) | |
| parent | 9c17a6d28b4acf044f408a0c7211e051e238c797 (diff) | |
| download | tor-fcdec00685608c85161116bdb7408f33094ea3fa.tar.gz tor-fcdec00685608c85161116bdb7408f33094ea3fa.zip | |
Merge branch 'maint-0.3.2'
Diffstat (limited to 'src/or/scheduler.c')
| -rw-r--r-- | src/or/scheduler.c | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/src/or/scheduler.c b/src/or/scheduler.c index 0bc827e276..cd047d5a75 100644 --- a/src/or/scheduler.c +++ b/src/or/scheduler.c @@ -258,9 +258,10 @@ select_scheduler(void) /* We should only log this once in most cases. If it was the kernel * losing support for kist that caused scheduler_can_use_kist() to * return false, then this flag makes sure we only log this message - * once. If it was the consensus that switched from "yes use kist" to - * "no don't use kist", then we still set the flag so we log once, but - * we unset the flag elsewhere if we ever can_use_kist() again. + * once. If it was the consensus that switched from "yes use kist" + * to "no don't use kist", then we still set the flag so we log + * once, but we unset the flag elsewhere if we ever can_use_kist() + * again. */ have_logged_kist_suddenly_disabled = 1; log_notice(LD_SCHED, "Scheduler type KIST has been disabled by " |