Dear list,
I am upgrading from Bering uClibc 2.2.2 to 2.3 on a WRAP platform.
Most things are working well, but I am having trouble with the ntp
system. My old system had ntpdate (ran at boot to set the LEAF box) and
ntpsimpl to provide ntp services to all my LAN clients (I am not saying
this is correct, it's just how I had it apparently working). Under 2.3
ntpdate throws a boot-time error :
"Running ntpdate to synchronize clockError : Name or service not known"
Starting it by hand gives:
# ntpdate -v de.pool.ntp.org
1 Jan 02:11:32 ntpdate[15298]: ntpdate [EMAIL PROTECTED]:4.2.0a+stable-8-r Mon
Mar 28 17
:57:03 CEST 2005 (1)
1 Jan 02:11:32 ntpdate[15298]: the NTP socket is in use, exiting
#
Killing the running ntp daemons allows ntpdate to function, but I want
both initial time sync for the box and server functionality for the LAN.
If I remove ntpdate from leaf.cfg and reboot I have no ntp function
whatsoever
/var/log/ntpd has:
1 Jan 02:09:01 ntpd[15446]: signal_no_reset: signal 17 had flags 4000000
1 Jan 02:09:01 ntpd[15446]: ntpd exiting on signal 15
1 Jan 02:09:01 ntpd[22353]: ntpd exiting on signal 15
1 Jan 02:09:03 ntpd[25476]: signal_no_reset: signal 17 had flags 4000000
1 Jan 02:09:05 ntpd[25476]: signal_no_reset: signal 14 had flags 4000000
Which I have not been able to interpret (yet); ntpd is still running,
even though the log mentions exiting but does not contact the Internet.
ps ax gives:
PID Uid VmSize Stat Command
1 root 252 S init [2]
2 root SW [keventd]
3 root SWN [ksoftirqd_CPU0]
4 root SW [kswapd]
5 root SW [bdflush]
6 root SW [kupdated]
23704 root 288 S /sbin/syslogd -m 240
6961 root 360 S /sbin/klogd
2977 root 516 S /usr/sbin/pppd call dsl-provider eth0
4886 root 436 S /usr/sbin/ntpd -g
25476 root 440 S /usr/sbin/ntpd -g
28163 root 328 S /usr/sbin/dropbear -p 22 -r
/etc/dropbear/dropbear_rs
3600 root 148 S /usr/sbin/watchdog
10111 nobody 344 S /usr/sbin/dnsmasq
3491 root 284 S /usr/sbin/inetd
15280 root 292 S /usr/sbin/ulogd -d
14485 root 300 S /usr/bin/ez-ipupdate -c /etc/ez-ipupd.conf -F
/var/ru
24440 sh-httpd 316 S /usr/sbin/mini_httpd -C /etc/mini_httpd.conf
16026 root 308 S /usr/sbin/cron
9765 root 284 S -sh
6088 root 452 S /usr/sbin/dropbear -p 22 -r
/etc/dropbear/dropbear_rs
16420 root 268 S sh -c /bin/sh
10396 root 276 S /bin/sh
29242 root 460 S /usr/sbin/dropbear -p 22 -r
/etc/dropbear/dropbear_rs
30408 root 284 S -sh
5902 root 280 S /bin/sh /usr/sbin/lrcfg
22592 root 452 S /usr/sbin/dropbear -p 22 -r
/etc/dropbear/dropbear_rs
8918 root 268 S sh -c /bin/sh
5446 root 276 S /bin/sh
9973 root 300 R ps ax
my leaf.cfg is:
LRP="root config etc local modules iptables dnsmasq ppp pppoe libm
libpcap keyboard shorwall ulogd dropbear mhttpd ncurses bash ntpsimpl
ezipupd tcpdump webconf"
PKGPATH="/dev/hda1:msdos"
syst_size=16M
log_size=4M
Visiting the ntp web site I read that a: it is common to use ntpdate to
kickstart the system and then ntpd to hold it on course BUT b: they
cannot run together on the same machine.
Have I got a problem with boot order or something fundamental here?
I would be glad of any suggestions.
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/
