Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Installation - Getting started with Red Hat Linux
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
synchronizing failed

synchronizing failed

2003-07-06       - By Telford

 Back
Reply:     1     2     3     4  

> Message: 4
> From: "Hattie Rouge" <redhat@(protected)>
> To: <psyche-list@(protected)>
> Subject: RE: synchronizing failed
> Date: Thu, 3 Jul 2003 15:07:22 -0700
> Reply-To: psyche-list@(protected)
>
> I bet you don't have an IP address 127.127.1.0 available on your net and
> the failure is because it couldn't connect.

I'll bet no one has an IP address 127.127.1.0 available because it is
inside the loopback domain... however for ntp.conf the 127.127.x.x subnet
is magical and would never attempt to make a connection.

> If all you are trying to do is keep your local LAN in sync, you can pick
> one machine and use rdate in cron to sync the rest to it.

That is what he is trying to do, it requires at least one machine to have
a 127.127.x.x line of some sort. My guess is that at least some "restrict"
commands are required, even if only to open up permissions to everyone.

Turn debugging on, read /usr/share/doc/ntp-4.1.1a/debug.htm

  - Tel




Earn $52 per hosting referral at Lunarpages.