Eric Spakman schrieb:
Bob,
Changing the package order in leaf.cfg won't change anything indeed. You
have to change the bootorder, which can be done by editing the
/etc/init.d/ files (ntpdate and ntp)
The RCDLINKS= line defines when in the bootprocess the daemon is started.
In the case of ntpdate this is "2,S51" and in the case of ntpd this is
"2,S23". This means that ntpd is started before ntpdate. If you want to
start ntpdate before ntpd you can try something like:
RCDLINKS="2,S21" in /etc/init.d/ntpdate
That make sure that ntpdate is started before ntpd (level 21 is before
level 23).
Don't forget to backup ntpdate.lrp after this change.
Eric Spakman
Bob,
thanks for your reply. As you can see from the process list, ntpd is
indeed started with the -g option (this is standard in the LEAF package).
It is still failing. Sadly the ntp site doesn't give much of a clue as to
the meaning of the log messages I get:
" 1 Jan 01:27:55 ntpd[21176]: signal_no_reset: signal 14 had flags
4000000"
Changing the package boot order (in leaf.cfg) doesn't seem to change
things either.
I have removed ntpdate (which was only to speed up initial time setting
- the WRAP board has no clock chip so it must always be set from ntp if
you want any sense in the log files). This also makes no difference, the
ntp daemon just doesn't start up properly. I'd be grateful for any more
ideas.
Bob
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
Thanks for the tip, Eric.
Do you know what the Sxx versus Kxx entries mean here and is the number
arbitrary (where can I find documents)?
This did solve the problem after I resolved a completely different one.
I will report it, as it may well be of interest to others:
Upon booting, the LEAF-WRAP box loads it's kernel, mounts drives
(Compact Flash here) and gets the packages.
These are then started according to priorities in /etc/init.d/ , as you
rightly pointed out. Sadly my internet provider (t-online) seems to
require a delay after disconnecting (this is not documented anywhere, I
just found it by trial and error). Without a minute or two delay, the
pppoe logon is refused several times until the persistence of the LEAF
box wins and a logon is achieved. Unfortunately ntpdate and ntpsimpl
have given up all hope of getting to an internet server and exited by then.
While investigating, I visited the ntp.org site and found that they now
deprecate ntpdate, preferring ntpd -g as a replacement. This is the
standard in LEAF anyway, so ntpdate has gone from my setup (sequencing
error thus resolved) and all is working as it should. I am still
disturbed about my ISP because a short power down would cause my LEAF
box (and thus the whole LAN) to lose time, making the logs almost
meaningless. Perhaps a power-up delay could be programmed.
Once again, thanks for the help.
Bob von Knobloch
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
