diff options
| author | Nick Mathewson <nickm@torproject.org> | 2017-11-17 09:57:15 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2017-11-17 09:57:15 -0500 |
| commit | 9fbc835f10e9fba6a9b0c6643a41aee9c8aa05c2 (patch) | |
| tree | 2f779595b328980c2fd7323e52649cab9a8680d9 /src/or | |
| parent | 2cee26b16447c143333ffc16502ecc28b48060cd (diff) | |
| download | tor-9fbc835f10e9fba6a9b0c6643a41aee9c8aa05c2.tar.gz tor-9fbc835f10e9fba6a9b0c6643a41aee9c8aa05c2.zip | |
Fix a wide comment
Diffstat (limited to 'src/or')
| -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 dabac386db..cbf51447bf 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 " |