Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
08-04-2010, 08:43 AM
|
#1
|
Senior Member
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
|
NTP Log Error Beginning in Slackware 13.1
This is a new one to me.
Code:
cat /tmp/ntp.log
3 Aug 17:07:23 ntpd[1615]: proto: precision = 0.619 usec
3 Aug 17:07:23 ntpd[1615]: line 28 column 19 syntax error, unexpected T_EOC, expecting T_Ipv4_flag or T_Ipv6_flag or T_String
3 Aug 17:07:23 ntpd[1615]: syntax error in /etc/ntp.conf line 28, column 19
3 Aug 17:07:23 ntpd[1615]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
3 Aug 17:07:23 ntpd[1615]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Line 28 is
Code:
multicastclient # listen on default 224.0.1.1
Never seen that error before, always just used the default /etc/ntp.conf file adding servers:
Code:
#server pool.ntp.org
server 0.us.pool.ntp.org
server 1.us.pool.ntp.org
server 2.us.pool.ntp.org
Have I missed something all these years? Thing works just fine, syncs up, rolls pool servers, does all it's supposed to.
|
|
|
08-04-2010, 11:36 AM
|
#2
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,260
Rep:
|
I noticed that line 27 (after adding three lines as you did) shows:
Code:
driftfile /etc/ntp/drift
But /etc/ntp/drift doesn't exist on my system.
May be "touch /etc/ntp/drift" and see what happens ?
|
|
|
08-05-2010, 07:27 AM
|
#3
|
Senior Member
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
|
I've always "touched" /etc/ntp/drift on a new install -- NTPD is supposed to do that on its own, but... what the heck, save trouble.
What I've typically done (for, oh, about 20 years now) is
Code:
cat 0 > /etc/ntp/drift
and that seems to have dealt with a lot of nonsense on various servers of various vintage of various operating systems.
That multicastclient line has been sitting there in ntp.conf files since, uh, I dunno, a log time. Never seen the error before, just kind of wondering what's up with it.
|
|
|
08-06-2010, 09:10 PM
|
#4
|
Member
Registered: Jan 2004
Location: Los Angeles
Distribution: Slack64 14.1
Posts: 581
Rep:
|
Just switched over to 13.1 today, and noticed exactly the same thing.
And no, it's got nothing to do with /etc/ntp/drift because I have that file, and I still get the error.
Cheers.
|
|
|
08-07-2010, 04:02 AM
|
#5
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
You should be able to see /usr/doc/ntp-4.2.6p1/html/confopt.html on your machine.
Quote:
multicastclient address [...]
Enable reception of multicast server messages to the multicast group address(es) (type m) specified. Upon receiving a message for the first time, the multicast client measures the nominal server propagation delay using a brief client/server exchange with the server, then enters the broadcast client mode, in which it synchronizes to succeeding multicast messages. Note that, in order to avoid accidental or malicious disruption in this mode, both the server and client should operate using symmetric key or public key authentication as described in the Authentication Options page.
|
I assume that older versions of ntpd didn't complain if you were missing the address.
|
|
|
08-07-2010, 05:12 AM
|
#6
|
Member
Registered: Jul 2007
Location: Nottingham, UK
Distribution: Slackware64-current
Posts: 93
Rep:
|
Quote:
Originally Posted by tronayne
This is a new one to me.
Line 28 is
Code:
multicastclient # listen on default 224.0.1.1
|
As it was a syntax error, then there could wrong with the spelling, something missing from the line or some other error. Maybe the "multicast" directive no longer knows the default - so I changed the line to:
Code:
multicastclient 224.0.1.1 # listen on default 224.0.1.1
The error message has disappeared and ntp seems to be working normally. Don't know if I've upset anything else though :-(
Regards
Phil
|
|
|
All times are GMT -5. The time now is 07:35 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|