Page 1 of 1

Error message after starting ntp

PostPosted: Mar 22nd, '14, 20:43
by linuxdad
I received the following message after starting up NTP.

server does not have extension for -dpms option

I cannot find the -dpms or +dpms option anywhere.

If this is for Display Power management, what does this have to do with MCC editing and starting NTP?

Re: Error message after starting ntp

PostPosted: Mar 22nd, '14, 23:28
by martinw
I'm guessing here, but when you start up NTP, it will adjust the system clock. If it moves the clock forward by a large amount, this could trigger display blanking. So it is likely that the script that starts the NTP daemon tries to temporarily disable display power management.

Re: Error message after starting ntp

PostPosted: Mar 23rd, '14, 18:22
by linuxdad
Ouch, that's kinda of scary. Reminds me of the tight integration that Windows has with the Registry.

Thanks for the reply.

Re: Error message after starting ntp

PostPosted: Mar 24th, '14, 01:21
by doktor5000
Where did you exactly receive that message?
When you run drakxservices, it will examine the state of all services, so this message may come from some completely different service,
and it only appeared because you changed something so drakxservices went through the list of all services again.

Also, I don't see ntp service here - only ntpd and ntpdate - or do you run a local ntp server?
I've just stopped and started ntpd again, and no message whatsoever.

I'd say it's a red herring, if you don't proof otherwise :)

Re: Error message after starting ntp

PostPosted: Mar 24th, '14, 22:44
by martinw
I can save linuxdad some effort, as I found a few spare minutes to check my guess:
  • /usr/bin/drakclock calls /usr/libexec/drakclock
  • /usr/libexec/drakclock calls any::disable_x_screensaver() before starting the NTP server and any::enable_x_screensaver after updating the system clock
  • disable_x_screensaver() runs xset -dpms and enable_x_screensaver() runs xset +dpms (in /usr/lib/libDrakX/any.pm)
@linuxdad, what happens when you type
Code: Select all
xset -dpms

on the command line. Here it runs without error.

I don't follow your comment about the WIndows registry. This is just a bit of user-friendliness on the part of the drak tools (MCC) - if it didn't do this, the screensaver or display blanking might activate when you enabled NTP.

Re: Error message after starting ntp

PostPosted: Jun 24th, '14, 14:02
by aevertett
Is it just a coincidence that this message appeared when NTP was started. I've done quite a bit of work with the NTP protocol and NTP servers and never come across this messages or indeed the dpms parameters.

Eve
edit doktor5000: removed advertising link