Hi!

Bug #593429 does not explain very well why the severity is serious. From
my understanding, the  reason is just bug #306106. Why  not just set the
severity of bug #306106 to serious?

Bug #593429  was created on August  2010. Last update of  bug #306106 is
September 2007.  It contains an  URL to a  patch. The patch seems  to be
available here:
 
http://dtucker.freeshell.org/openntpd/patches/openntpd-3.6.1p1-linux-adjtimex.patch

There is  no explanation on  why this patch  does not solve  #306106. It
does not  apply cleanly to current  openntpd 3.9p1. Maybe  there is some
updated version?

openntpd is working  fine for me. Does #306106  still applies to current
openntpd versions?   Can we tell  in what conditions  it is not  able to
synchronize correctly?   If those conditions are pretty  rare, maybe the
severity could be  important instead of serious. I  personnaly prefer to
use openntpd instead of ntpd because of its security record (no security
hole according to  Debian security tracker vs 6  security holes in ntpd)
and its cleaner and simple design.
-- 
THE BOYS ROOM IS NOT A WATER PARK
THE BOYS ROOM IS NOT A WATER PARK
THE BOYS ROOM IS NOT A WATER PARK
-+- Bart Simpson on chalkboard in episode 3F03

Attachment: pgpNNuMNTiExm.pgp
Description: PGP signature

Reply via email to