hwclock bug #74

[Peter S. Mazinger]

On Tue, 27 Sep 2005, Paul Fox wrote:

>  > > can we close this bug?
>  > >
>  > > i believe that the current busybox hwclock applet is behaving
>  > > correctly, and, indeed, it matches the behavior of any
>  > > /sbin/hwclock i've found.
>  > 
>  > please do ... i never managed to get my head around those hwclock bugs 
>  > (there's a couple open atm actually, so if you could review all of them ...)
> 
> i only see the one.  are you sure they're busybox bugs, and not uclibc?
> i don't do uclibc.
> 
>  > > i think the only issue to be resolved with hwclock, if any, is
>  > > whether it should be trying to open /etc/adjtime (traditional) or
>  > > /var/lib/hwclock/adjtime (current behavior).
>  > 
>  > i think we should either add support for both:
>  > FILE *fp = fopen(/var/lib/hwclock/adjtime)
>  > if (!fp) fp = fopen(/etc/adjtime)
>  > 
>  > or add a config option so you can select which one you want ... anyone care 
>  > either way ?
> 
> i don't care either.  is the /var/lib path a "standard" of some
> sort?  if so i'd say try both.

/etc/adjtime is obsoleted, /var/lib/... is FHS.

Peter

> 
> it'll waste some bytes, but we'll put tito on the job and he'll get 'em
> back for us.  ;-)
> 
> paul
> =---------------------
>  paul fox, pgf at brightstareng.com
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
> 
> 

-- 
Peter S. Mazinger <ps dot m at gmx dot net>           ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08  BB6E C389 975E A5F0 59F2