Joseph Gwinn <[EMAIL PROTECTED]> writes:
>In article <[EMAIL PROTECTED]>,
> "Peter J. Cherny" <[EMAIL PROTECTED]> wrote:
>> Joseph Gwinn wrote:
>> >...
>> > Which brings me to a question: How does one get NTP to tell you exactly
>> > where it is getting such things as the ntp.conf file from, all without
>> >...
>> [EMAIL PROTECTED] ~]$ strings /usr/sbin/ntpd|grep ntp.conf
>> /etc/ntp.conf
>In the RHEL case, this would find exactly the wrong copy of ntp.conf,
>being the one we were changing to no avail, not the one that NTP was in
>fact using.
Which one was ntp in fact using?
>> [EMAIL PROTECTED] ~]$ strace -f -o x /usr/sbin/ntpd -g
>I'll have to look into this. It sounds like it might be general enough.
>
>> [EMAIL PROTECTED] ~]# grep ntp.conf x
>> 3351 open("/etc/ntp.conf", O_RDONLY) = 4
>Doesn't this assume that the correct "ntp.conf" file is called ntp.conf?
>It may be common, the standard convention, but it is not required.
>The whole point is to find the correct file without making assumptions,
>because on a strange computer strange things may have been done.
yes, but then do strace as above and look through the file looking for
something that might be a configuration file. If they call it /lib/libc.so
then you are probably shit out of luck, but usually they will not do that.
>Thanks,
>Joe Gwinn
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.org/mailman/listinfo/questions
