On Mon, 2011-08-22 at 10:37 -0700, Hugo Silva wrote:
> On 08/22/11 16:43, DeuZa wrote:
> > 2011/8/22 Hugo Silva
> >
> >> Hello,
> >>
> >
> > Hello Hugo, I was in the same cas (I think)
> > I use a workaround on my VPS :
> >
> > machdep.independent_wallclock: 1
> >
> > And the ntpd is fine now,
On 08/22/11 16:43, DeuZa wrote:
> 2011/8/22 Hugo Silva
>
>> Hello,
>>
>
> Hello Hugo, I was in the same cas (I think)
> I use a workaround on my VPS :
>
> machdep.independent_wallclock: 1
>
> And the ntpd is fine now, I know it's just a workaround, but practice for
> running ntpd on Xen instan
2011/8/22 Hugo Silva
> Hello,
>
Hello Hugo, I was in the same cas (I think)
I use a workaround on my VPS :
machdep.independent_wallclock: 1
And the ntpd is fine now, I know it's just a workaround, but practice for
running ntpd on Xen instances
Regards,
--
Alain AUDEBERT aka 2A
__
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
Hello,
During my tests with 9.0, I have found another issue that I would like
to bring your attention to.
On all three 9.0-BETA1 virtual machines installed (on a NetBSD dom0,
should it matter) I'm encountering the infamous 'runtime went backwards'
messages (the VM's been up for days, it seems to
