[Pm-utils] [PATCH 8/8] pm-utils 1.2.3 proposed patches

[Robby Workman]

On Sun, 30 Nov 2008 12:54:30 -0600
Victor Lowther <victor.lowther at gmail.com> wrote:

> On Nov 30, 2008, at 10:42 AM, "Dan Nicholson" <dbn.lists at gmail.com>  
> wrote:
> 
> > On Sun, Nov 30, 2008 at 8:00 AM, Victor Lowther
> > <victor.lowther at gmail.com> wrote:
> >> On Nov 29, 2008, at 2:32 PM, "Dan Nicholson"
> >> <dbn.lists at gmail.com> wrote:
> >>>
> >>> Well, I'll try sending a mail to alsa-devel and see if anything  
> >>> happens.
> >>
> >> Ok, but the alsa hook is pretty fast, so  it is lower on my list of
> >> priorities.
> >
> > Yeah, it's not a big deal. At least, I think it should only be run
> > if requested. Like NEED_SOUND_RESTORE or something. I'm sure it got
> > blocked from getting back to this list, but here's Takashi's reply
> > about needing the hook:
> >
> > http://mailman.alsa-project.org/pipermail/alsa-devel/2008-November/013030.html
> >
> >> I will probably release an updated 1.2.3 patch series later
> >> today. I missed
> >> the slackware init system support patch, I made 50ntpd faster in  
> >> the fast
> >> path (it is still an ugly hack, tho), and there are some doc  
> >> updates as
> >> well.
> >
> > Yeah, go ahead and release. More releases can always be made later.
> > What would it take to find if 50ntpd can be removed? I personally
> > think it's a waste of time, but maybe I'm missing the real reason
> > for it's existence. Should I ask on the ntp list?
> 
> Well, this code also seems to go all the way back to the initial  
> checkin, and based on the commit log comments it is there to try and  
> fix any clock drift the system may have experienced while asleep.
> 
> If we had a way to just tell ntpd to sync at the next oppourtunity,  
> this hook would be much less ugly. However, it seems that there is
> no such way, so restarting ntpd is the only option, aside from just  
> letting sync according to its usual schedule.
> 
> Since we don't, it may be best to drop this hook, just let ntpd  
> continue to sync according to its internal schedule, and consider  
> getting networkmanager to kick ntpd for us whenever the internet is  
> back up.


The only concern I have with this is for those cases where people don't
use NetworkManager, but I guess the other network management utility
that they *do* use should implement this.  Personally, I like the first
idea of just dropping the hook and letting ntpd handle it on its own.

-RW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/pm-utils/attachments/20081130/a8441c5c/attachment.pgp