hwclock bug #74

[Paul Fox]

 > > 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.

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