[EMAIL PROTECTED] writes:
> On Wed, Feb 01, 2006 at 07:25:35PM +, James wrote:
>> ntpq -p
>> remote refid st t when poll reach delay offset
>> jitter
>> ==
>> ecoca.eed.usv.r 80.96.120.253
On Wed, Feb 01, 2006 at 07:25:35PM +, James wrote:
> ntpq -p
> remote refid st t when poll reach delay offset jitter
> ==
> ecoca.eed.usv.r 80.96.120.2532 u8 641 202.639 1436722
Default behaviour is that if the time zone is off by more than a preset
amount (I think 128ms) it will refuse to sync, and silently fails.
Read the docs for the config file command "tinker panic 0" (and its
implications) which will remove the limitation and allow stepping to the
new time.
Also nt
On Feb 1, 2006, at 2:18 PM, James wrote:
James tampabay.rr.com> writes:
John Jolet jolet.net> writes:
But now when I run 'ntpq -p' I get:
ntpq: read: Connection refused
is ntpd dying? ps -elf|grep ntp should show you something besides
the grep.
Yep. Attempt stop it and start it agai
On 2/1/06, James <[EMAIL PROTECTED]> wrote:
> It corrected the minutes but it's off by exactly one hour. It needs to be
> EST (eastern standard time) NY (Tampa Florida).
>
> so what file do I edit to correct utc to est ?
Try timezone US/Eastern instead of EST.
ln -sf /usr/share/zoneinfo/US/Easte
James wrote:
is ntpd dying? ps -elf|grep ntp should show you something besides
the grep.
Yep. Attempt stop it and start it again: /etc/init.d/ntpd start
fails.
"/etc/init.d/ntpd zap" to clear out the invalid status, then do the
'start' again.
--
gentoo-user@gentoo.org mailing l
James tampabay.rr.com> writes:
>
> John Jolet jolet.net> writes:
>
> > > But now when I run 'ntpq -p' I get:
> > > ntpq: read: Connection refused
>
> > is ntpd dying? ps -elf|grep ntp should show you something besides
> > the grep.
>
> Yep. Attempt stop it and start it again: /etc/init.d/
John Jolet jolet.net> writes:
> > But now when I run 'ntpq -p' I get:
> > ntpq: read: Connection refused
> is ntpd dying? ps -elf|grep ntp should show you something besides
> the grep.
Yep. Attempt stop it and start it again: /etc/init.d/ntpd start
fails.
Ideas?
James
--
gentoo-user
On Feb 1, 2006, at 1:25 PM, James wrote:
Devon Miller gmail.com> writes:
Make sure you have told you firewall to allow port 123 for both TCP &
UDP.I had the same behavior until I did that.dcm
Well my firewall should allow outgoing initiated sessions from the
ntpd (internal) server. From wh
Devon Miller gmail.com> writes:
> Make sure you have told you firewall to allow port 123 for both TCP &
> UDP.I had the same behavior until I did that.dcm
Well my firewall should allow outgoing initiated sessions from the
ntpd (internal) server. From what I read, the remote ntpd server
does not
10 matches
Mail list logo