[ntp:questions] NTP 4.2.5p180 adds IPv6 support on Windows

Danny Mayer mayer at ntp.org
Mon Jun 1 11:44:10 UTC 2009

Maarten Wiltink wrote:
> "David J Taylor"
> <david-taylor at blueyonder.not-this-part.nor-this.co.uk.invalid> wrote in
> message news:9bLUl.36424$OO7.26643 at text.news.virginmedia.com...
> [...]
>> So, one question which now arises is:  how should the current Windows
>> NTP handle the libeay32.dll version issue?  Having it packaged with
>> Meinberg's distribution, and putting it into the application directory
>> seems to be an approach which works.
> And it does. That other Windows installation had no problems.
>> Should those installing by copying ntpd.exe etc. from Zip archives
>> be expected to look after libeay32.dll themselves?  Should the
>> bindings be dynamic rather than static so that ntpd can fall back
>> if the required entry point or even the DLL isn't available?
>> Should the "correct" version of libeay32.dll always be included
>> with the Zip archive?
> Speaking as a user, it seems kind of silly not to include parts
> without which things don't work.
> My logic was that if this DLL wasn't included, it was something
> external, and would be stable enough that a copy from an older
> version should work - perhaps five and a half years _is_ stretching
> it, but I felt sure enough that when it didn't work, I assumed
> there was another problem.
> The point being, this is a not very dumb user working with what
> he has, and it doesn't work. Include the DLL, already.

If you are saying that Meinberg didn't include it, then we need to ask
them to do so since it won't work without it.


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

More information about the questions mailing list