immediately have
signal. If your ppp label is called gprs for example, in
/etc/ppp/ppp.linkup
add
gprs:
! /usr/sbin/ntpdate -s
---Mike
ntpdate_enable="YES"
ntpdate_flags="-b "
into rc.conf. Problem is, ntpdate timeouts, because network starts slowly in
this cas
Hi,
I have a box connected via u3g (Huawei E169) running OpenVPN with PKI
certificates. It needs to synchronise time. I added
ntpdate_enable="YES"
ntpdate_flags="-b "
into rc.conf. Problem is, ntpdate timeouts, because network starts slowly in
this case. I need ntpdate t
In the last episode (Jul 16), Marc G. Fournier said: Figured it out ...
> - --On Monday, July 16, 2007 21:48:15 -0300 "Marc G. Fournier" <[EMAIL
> PROTECTED]>
> > rwhod generates no errors when I try to run it, and truss doesn't
> > show anything since it does a fork:
> >
> > stat("/etc/nsswitch.
start up as expected ...
- --On Monday, July 16, 2007 21:48:15 -0300 "Marc G. Fournier" <[EMAIL
PROTECTED]>
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Just looking over one of our AMD64 servers, and rwhod / syslog / ntpdate
> won't wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just looking over one of our AMD64 servers, and rwhod / syslog / ntpdate won't
work on that server, although its running the same date/version ... I checked
securelevel, and they are both running the same ...
rwhod generates no errors when
On Wed, 9 May 2007, Ian Smith wrote:
Bottom line might be: if it hurts when you run powerd with APM,
don't.
If you want powerd to work, I'd suggest trying ACPI again
ok, using ACPI solved the clock problem, the suspend problem
has to be solved later
m.
On Thu, 3 May 2007, Martin Dieringer wrote:
> On Thu, 3 May 2007, Ian Smith wrote:
> >
> > > > Now I got following while playing sound on the Compaq:
> > > >
> > > > kernel: calcru: runtime went backwards from 183711700 usec to
> > > > 183167434 usec for pid 12 (swi4: clock sio)
> > > >
>
On Thu, 3 May 2007, Pieter de Goeje wrote:
On Thursday 03 May 2007, Martin Dieringer wrote:
# sysctl kern.timecounter
kern.timecounter.hardware: i8254
kern.timecounter.choice: TSC(-1000) i8254(0) dummy(-100)
To me it seems that you are running with acpi disabled. For example I have
this:
On Thursday 03 May 2007, Martin Dieringer wrote:
> # sysctl kern.timecounter
> kern.timecounter.hardware: i8254
> kern.timecounter.choice: TSC(-1000) i8254(0) dummy(-100)
To me it seems that you are running with acpi disabled. For example I have
this:
kern.timecounter.choice: TSC(800) ACPI-fa
On Thu, 3 May 2007, Ian Smith wrote:
> > Now I got following while playing sound on the Compaq:
> >
> > kernel: calcru: runtime went backwards from 183711700 usec to 183167434
usec for pid 12 (swi4: clock sio)
> >
> > here I have a working clock, but also intermittent sound output
To which I s
Sorry if it's just
> >>> me, but I am not quite clear about that, from what has been written
> >>> already.
> >>
> >> I would have to update every minute at least and would still be more
> >> than 5 seconds off.
> >
w ntpd works vs. how ntpdate works.
ntpd is a daemon, so you don't run it every minute, it runs in the
background and keeps the clock up to date.
Turn off all of the power management, and any other service that
might be affecting the clock, and then reboot. If your system is
able to maintai
On Wed, May 02, 2007 at 02:30:38PM -0700, Kevin Oberman wrote:
> A few more comments:
>
> If ntpd is started with the '-g' flag, it will initially step the time
> so you get your clock set as you would have with ntpdate. This is set in
> /etc/rc.conf as 'ntpd_flags
the following in /etc/rc.conf:
> >
> > ntpdate_enable="yes"
> > ntpdate_flags="-sb 1.2.3.4"
> > ntpd_enable="yes"
>
> Just a side note - according to the ntpdate(8) man page, ntpdate is
> deprecated and will eventually be removed fro
On Wed, May 02, 2007 at 10:23:09AM -0700, Doug Barton wrote:
[snip /etc/ntp.conf configuration file instructions]
> Then make sure you have the following in /etc/rc.conf:
>
> ntpdate_enable="yes"
> ntpdate_flags="-sb 1.2.3.4"
> ntpd_enable="yes"
time with frequent NTP syncronizations? Sorry if it's just
me, but I am not quite clear about that, from what has been written
already.
I would have to update every minute at least and would still be more
than 5 seconds off.
I think you misunderstand how ntpd works vs. how ntpdate works. ntpd
On Wed, 2007-05-02 at 04:04 +0200, Martin Dieringer wrote:
>
> the hiccups have reappeared, so they are not related to powerd.
>
> I still have 0.5 seconds time offsets after 10 minutes, on the
> thinkpad, without powerd...
>
> m.
I think the two effects (losing time, sound hiccups) are unrelat
On Wed, 2 May 2007, Martin Dieringer wrote:
[chomping, ccs too]
> >> > >>> I get about half a second time offsets after 10 seconds, and more
> >> > >>> than 100s after half an hour or so.
> >> > >>> I think it has to do with powerd, if I kill that, the time stays
> >> correct.
> >> > >>> It
On Wed, 2 May 2007, Martin Dieringer wrote:
On Wed, 2 May 2007, Ian Smith wrote:
On Wed, 2 May 2007, Martin Dieringer wrote:
> On Tue, 1 May 2007, Martin Dieringer wrote:
>
> > On Tue, 1 May 2007, Clayton Milos wrote:
> >
> >>> Hi,
> >>>
> >>> I get about half a second time offsets after 10
On Wed, 2 May 2007, Ian Smith wrote:
On Wed, 2 May 2007, Martin Dieringer wrote:
> On Tue, 1 May 2007, Martin Dieringer wrote:
>
> > On Tue, 1 May 2007, Clayton Milos wrote:
> >
> >>> Hi,
> >>>
> >>> I get about half a second time offsets after 10 seconds, and more
> >>> than 100s after half an
On Wed, 2 May 2007, John Walthall wrote:
On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
I think it has to do with powerd, if I kill that, the time stays correct.
With powerd enabled, are you able to maintain a "reasonably"
correct time with frequent NTP syncronizations?
On Wed, 2 May 2007, Martin Dieringer wrote:
> On Tue, 1 May 2007, Martin Dieringer wrote:
>
> > On Tue, 1 May 2007, Clayton Milos wrote:
> >
> >>> Hi,
> >>>
> >>> I get about half a second time offsets after 10 seconds, and more
> >>> than 100s after half an hour or so.
> >>> I think it
Compaq nc4000 and an IBM ThinkPad T42p laptop.
>
> Can this be solved?
> thanks
> m.
You have the option of running ntpd instead of ntpdate. This assures a
continous polling against the server. IIRC ntpd would solve the clock
skew via ntp.drift.
--
H
On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
> I get about half a second time offsets after 10 seconds, and more
> than 100s after half an hour or so.
> I think it has to do with powerd, if I kill that, the time stays correct.
> It happens both on a Compaq nc4000 and an IBM
On Tue, 1 May 2007, Martin Dieringer wrote:
On Tue, 1 May 2007, Clayton Milos wrote:
Hi,
I get about half a second time offsets after 10 seconds, and more
than 100s after half an hour or so.
I think it has to do with powerd, if I kill that, the time stays correct.
It happens both on a Compaq
On Tue, May 01, 2007 at 08:50:10PM +0200, Martin Dieringer wrote:
> I think it has to do with powerd, if I kill that, the time stays correct.
With powerd enabled, are you able to maintain a "reasonably" correct time with
frequent NTP syncronizations? Sorry if it's just me, but I am not quite clea
On Tuesday 01 May 2007 18:10:38 Martin Dieringer wrote:
> not to mention the energy waste
power off solve this if it is really your issue ... :S
--
João
A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik https://datacent
On Tue, 1 May 2007, Clayton Milos wrote:
Hi,
I get about half a second time offsets after 10 seconds, and more
than 100s after half an hour or so.
I think it has to do with powerd, if I kill that, the time stays correct.
It happens both on a Compaq nc4000 and an IBM ThinkPad T42p laptop.
Can t
Hi,
I get about half a second time offsets after 10 seconds, and more
than 100s after half an hour or so.
I think it has to do with powerd, if I kill that, the time stays correct.
It happens both on a Compaq nc4000 and an IBM ThinkPad T42p laptop.
Can this be solved?
thanks
m.
This has got to
Hi,
I get about half a second time offsets after 10 seconds, and more
than 100s after half an hour or so.
I think it has to do with powerd, if I kill that, the time stays correct.
It happens both on a Compaq nc4000 and an IBM ThinkPad T42p laptop.
Can this be solved?
thanks
m.
_
On Thu 2006-03-30 (13:22), jdow wrote:
> If you have ntpd running, which is the right way to do it anyway, then
> ntpdate cannot run unless you tell it to use a different port than the
> ntp port because it's already in use. "ntpdate -q -u pool.ntp.org" should
> work
ources.
hah, that did the trick, thanx ;)
ps. i went back and changed 'sock' in /usr/src/contrib/ntp/ntpdate/ntpdate.c
from
'-1' back to '0', recompiled, and yea changing 'sock' doesn't make any
difference
(in this respect).
__
From: "gareth" <[EMAIL PROTECTED]>
On Thu 2006-03-30 (10:35), Michael Proto wrote:
cd /usr/src/usr.sbin/ntp
make depend
make
make install
yay, ok that works ta (going into /usr/src/usr.sbin/ntp
as opposed to /usr/src/usr.sbin/ntp/ntpdate) and the
binary gets rebuilt. b
hat works ta (going into /usr/src/usr.sbin/ntp
> as opposed to /usr/src/usr.sbin/ntp/ntpdate) and the
> binary gets rebuilt. but, same problem :/
>
> # ntpdate nom.uct.ac.za
> Looking for host nom.uct.ac.za and service ntp
> host found : 2001:4200:300:100:20e:cff:fe5c:f5c4
> 30 M
On Thu 2006-03-30 (18:24), gareth wrote:
> > Perhaps someone with a better knowledge of the resovler can answer to
> > why no ipv4 address is returned.
>
> yea. i get the ipv4 addy back from my linux machines.
sorry that wasn't clear - when i run 'ntpdate nom.uct.ac
On Thu 2006-03-30 (11:18), Michael Proto wrote:
> Just curious, do you have ipv6 enabled in your kernel and working on
> your Ethernet interface? It looks like you're only getting an ipv6
> address returned by the resolver for nom.uct.ac.za. I did a lookup
> myself and I got both an ipv4 and ipv6 a
t; cd /usr/src/usr.sbin/ntp
>> make depend
>> make
>> make install
>
> yay, ok that works ta (going into /usr/src/usr.sbin/ntp
> as opposed to /usr/src/usr.sbin/ntp/ntpdate) and the
> binary gets rebuilt. but, same problem :/
>
> # ntpdate nom.uct.ac.za
> Lookin
On Thu 2006-03-30 (10:35), Michael Proto wrote:
> cd /usr/src/usr.sbin/ntp
> make depend
> make
> make install
yay, ok that works ta (going into /usr/src/usr.sbin/ntp
as opposed to /usr/src/usr.sbin/ntp/ntpdate) and the
binary gets rebuilt. but, same problem :/
# ntpdate nom.uct.a
On Thursday 30 March 2006 10:31, gareth wrote:
> On Thu 2006-03-30 (08:54), Scot Hetzel wrote:
> > 2. change to sub directory where FreeBSD builds ntpdate:
> > cd /usr/src/usr.sbin/ntp/ntpdate
> > make clean
Add "make depend" at this point.
> > m
cd /usr/src/usr.sbin/ntp
make depend
make
make install
gareth wrote:
> On Thu 2006-03-30 (08:54), Scot Hetzel wrote:
>> 2. change to sub directory where FreeBSD builds ntpdate:
>> cd /usr/src/usr.sbin/ntp/ntpdate
>> make clean
>> make
>> make in
On Thu 2006-03-30 (08:54), Scot Hetzel wrote:
> 2. change to sub directory where FreeBSD builds ntpdate:
> cd /usr/src/usr.sbin/ntp/ntpdate
> make clean
> make
> make install
> make clean
cool, thanx, i found that earlier with a 'locate ntpdate | grep
On 3/30/06, gareth <[EMAIL PROTECTED]> wrote:
> hey guys, i get a problem from ntpdate saying:
>
> ntpdate[34131]: cannot find family compatible socket to send ntp packet
>
> and i got a tip off google awhile back and changed 'sock' in
> /usr/src/contrib/ntp/ntpda
hey guys, i get a problem from ntpdate saying:
ntpdate[34131]: cannot find family compatible socket to send ntp packet
and i got a tip off google awhile back and changed 'sock' in
/usr/src/contrib/ntp/ntpdate/ntpdate.c from '0' to '-1'. but now, how
do i r
] ***
-- Forwarded message --
Date: Fri, 14 Mar 2003 10:23:35 +0100 (CET)
From: Dirk-Willem van Gulik <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: conf/5: ntpdate not ran before (x)ntpd
>Number:
On Wed, May 24, 2000 at 07:48:03PM +, Wilko Bulte wrote:
> On Wed, May 24, 2000 at 10:15:21AM -0700, Glen Gross wrote:
> > I have had the same experience, with a DSL line. I don't know if
> > ntpdate requires the time to be within a certain threshold before
> >
45 matches
Mail list logo
