RFC: New event timers infrastructure

Brandon Gooch jamesbrandongooch at gmail.com
Mon Jun 21 12:19:34 UTC 2010

On Mon, Jun 21, 2010 at 12:33 AM, Alexander Motin <mav at freebsd.org> wrote:
> Brandon Gooch wrote:
>> On Sun, Jun 20, 2010 at 3:35 PM, Doug Barton <dougb at freebsd.org> wrote:
>>> On 06/20/10 08:47, Alexander Motin wrote:
>>>> While this can be done in sysctl.conf, it would be better to do it in
>>>> loader.conf to make it applied from the beginning, without on-the-fly
>>>> timers change.
>>> You're probably right that for something this fundamental it's better to do
>>> it in loader.conf, however I wanted to mention that I recently changed the
>>> rcorder for the "early" boot scripts to run sysctl first for very similar
>>> reasons.
>> This is good information, so sorry if I'm being dense: does this mean
>> that it should have worked by applying the changes via
>> /etc/sysctl.conf?
> "You are too old. You are already born." (c) Sergey Lukyanenko.
> stathz set much earlier, just before "Starting kernel event timers"
> logged first time. It can only be affected from loader.conf.

OK. I understand everything[*] now...

>> No worries though, I've set it in /boot/loader.conf to avoid any
>> possible ambiguity or anomalous behavior, and it's working very well!
> Nice.

Very nice :)

> BTW, I've successfully tested suspend/resume on my amd64 laptop with all
> timers.

For me, suspend/resume trials will be this evening, U.S. Central
Standard Time...

Looking forward to it!


[*] Well, almost everything, except for the Russian Sci-Fi quote ;)

More information about the freebsd-current mailing list