>>> In article <87bpsrtan7@thumper.dhh.gt.org>, John Hasler
>>> writes:
John> Harlan Stenn writes:
>> mlockall() and sched_setscheduler() should be discovered automatically by
>> the 'configure' step. I think mlockall() is the default on many OSes
>> that provide it, and the -N option proba
Harlan Stenn writes:
> mlockall() and sched_setscheduler() should be discovered automatically by
> the 'configure' step. I think mlockall() is the default on many OSes
> that provide it, and the -N option probably controls the priority
> setting.
mlockall() seems to be disabled under Linux in 4.2
kiran shirol wrote:
> NTP experts,
>
> I have a few queries regarding NTP.
>
I have a following setup.
> 1. Valid NTP server
> 2. Device1 where i configure a NTP server with "ntp server" command.
> 3. Another Device2 where I configure Device1's IP address in "ntp
> p
Rob van der Putten writes:
> Hi there
>
>
> Rob wrote:
>
>> So do a "stty -a > Then you should get this output:
>> speed 50 baud; rows 0; columns 0; line = 0;
>> intr = ; quit = ; erase = ; kill = ; eof =
>> ;
>> eol = ; eol2 = ; swtch = ; start = ; stop =
>> ;
>> susp = ; rprnt = ; werase = ;
Rob van der Putten wrote:
> Assuming of course, that ntpd doesn't reset the tty to the original
> values when stopped.
> Or should I do this with ntpd running?
Of course. You can do it at any time, I got the above output from my
own DCF77 receiver port.
Hi there
Rob wrote:
> So do a "stty -a
> Then you should get this output:
>
> speed 50 baud; rows 0; columns 0; line = 0;
> intr = ; quit = ; erase = ; kill = ; eof =
> ;
> eol = ; eol2 = ; swtch = ; start = ; stop =
> ;
> susp = ; rprnt = ; werase = ; lnext = ;
> flush = ; min = 1; time =
Rob van der Putten wrote:
> Hi there
>
>
> Rob wrote:
>
>> Most likely some stupid program has changed the settings of the COM port.
>> (especially the baudrate)
>>
>> For example, in SuSE Linux when you are so unfortunate to click on the
>> "hardware information" icon in YaST, everything is mess
Hi there
Rob wrote:
> Most likely some stupid program has changed the settings of the COM port.
> (especially the baudrate)
>
> For example, in SuSE Linux when you are so unfortunate to click on the
> "hardware information" icon in YaST, everything is messed up in the process
> of detecting wha
I’m looking for someone to write technical manuals for the
installation, setup and maintenance of the NTP server products my
company supplies.
This person would need to have a knowledge of NTP and networking and
past experience in writing manuals, preference to people living in the
west midlands (
Rob van der Putten wrote:
> Hi there
>
>
> From the syslog;
> Feb 24 15:24:05 sput ntpd[28039]: parse: convert_rawdcf: INCOMPLETE DATA
> - time code only has 3 bits
> Feb 24 15:24:05 sput ntpd[28039]: PARSE receiver #0: interval for
> following error message class is at least 00:01:00
> Feb 24
On Feb 23, 9:07 am, jlevine wrote:
>
> 2. Sending any reply at all doubles the network traffic and makes
> an
> attack more effective. Therefore, all of the NIST servers log the
> event and
> the source ip but do not respond. I think it is not appropriate for a
> national
> timing laboratory to
Hi there
From the syslog;
Feb 24 15:24:05 sput ntpd[28039]: parse: convert_rawdcf: INCOMPLETE DATA
- time code only has 3 bits
Feb 24 15:24:05 sput ntpd[28039]: PARSE receiver #0: interval for
following error message class is at least 00:01:00
Feb 24 15:24:05 sput ntpd[28039]: PARSE receiver #
12 matches
Mail list logo
