[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] Fwd: Re: gpsd for time sync on Ubuntu remix too hard for

From: Greg Troxel
Subject: Re: [gpsd-dev] Fwd: Re: gpsd for time sync on Ubuntu remix too hard for normals - how to improve?
Date: Wed, 08 May 2019 07:21:02 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (berkeley-unix)

"Gary E. Miller" <address@hidden> writes:

>> I think it's good to say something, but which OSes decide to enter
>> which powersave states based on what kind of userland activity seems
>> like a very broad brush.  So perhaps
>>   With -n, gpsd will continue to read from a receiver and process the
>>   data.  On some systems, this can prevent the system from entering
>> sleep. An example is FooOS, which [MAKING STUFF UP in its default
>>   configuration, detects processes using CPU time, and avoids
>> sleeping in that case.]
> I don't know of any OS where an actively running simple daemon does not
> stop sleeping.  There are OS where a daemon can tell the OS that it
> can be put to sleep, but gpsd is not smart enough to do that.
> So I inclined much more to Lisandro's wording.
> Maybe "will prevent" to "will likely prevent"?

My memory is fuzzy, but I'm pretty sure I''ve seen macs (macos) enter
sleep in the middle of a huge compilation.  My impression has been that
entering sleep is about timeouts from keyboard/mouse and the implied

Systems have all sorts of background processes, like syslog and cron.
So this may well be true, but it doesn't seem obviously sensible.

Hence my notion of something specific that can be looked up and the
details read about.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]