Re: ntpd vs selinux

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Gene Heskett:
>>> Jun 30 22:37:14 diablo ntpd[1936]: sendto(194.145.249.108): Invalid argument
>>> Jun 30 22:38:01 diablo ntpd[1936]: sendto(194.102.249.64): Invalid argument
>>> Jun 30 22:42:04 diablo ntpd[1936]: sendto(193.40.133.134): Invalid argument

Tim:
>> For what it's worth, I'd see the same sort of thing if NTP was run
>> twice.  Don't ask how that might happen, I've not figured it out.  If I
>> checked the running processes, killed off all the NTPDs then restarted,
>> it went away.
 
Gene Heskett:
> I didn't kill any extra ntpd's. just a regular 'service ntpd restart'

Another thing that has that effect, that I'd forgotten about since
leaving dial-up internet, was an interface going down that NTP was
using.  I had to put an NTP restart script into my ifup post PPP script,
to restart the NTP server after a new connection.  It just wouldn't keep
on working by itself.

-- 
(Currently running FC4, occasionally trying FC5.)

Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux