Am Samstag, 4. Dezember 2010, 16:25:18 schrieb davidMbrooke: > On Sat, 2010-12-04 at 15:12 +0100, KP Kirchdoerfer wrote: > > Am Samstag, 4. Dezember 2010, 14:13:25 schrieb davidMbrooke: > > > On Sat, 2010-12-04 at 12:20 +0100, KP Kirchdoerfer wrote: > > > > Hi David; > > > > > > > > Am Samstag, 4. Dezember 2010, 11:41:11 schrieb davidMbrooke: > > > > > Hi kp, > > > > > > > > > > Nice to see that someone reads the documentation :-) > > > > > > > > > > On Fri, 2010-12-03 at 07:32 +0100, KP Kirchdoerfer wrote: > > > > > > Hi David; > > > > > > > > > > > > "Boot-time "hang" at "Starting BusyBox ntpd". > > > > > > "With some system configurations the boot process can appear to > > > > > > "hang" at the message "Starting BusyBox ntpd". This is due to > > > > > > ntpd not being able to resolve an IP address for its default NTP > > > > > > server. After some delay this will time-out (with the message > > > > > > ntpd: bad address '0.pool.ntp.org') after which the boot process > > > > > > will continue. > > > > > > The problem is that the dnsmasq package is part of the default > > > > > > "LRP" package list in leaf.cfg, and so is dhcpcd but the two are > > > > > > not connected together in their default configuration. The > > > > > > solution is to configure dnsmasq to use the right "resolv-file" > > > > > > setting, as described here or to configure alternative packages > > > > > > as appropriate." > > > > > > > > > > > > Do I understand that this just happens during first boot/until > > > > > > the router/dnsmasq has been setup properly? > > > > > > > > > > Correct. > > > > > > > > > > > In that case we may change the default in /etc/default/ntpd to > > > > > > not start ntpd, until the user changes /etc/default/ntpd. > > > > > > BTW: Starting an image within qemu doesn't hang, ntpd just give a > > > > > > quick warning that it can't resolve the address.... > > > > > > > > > > > > kp > > > > > > > > > > I decided it was time to get to the bottom of this because I see > > > > > the same behaviour as you with qemu but a ~2 minute delay on my > > > > > physical test machine. > > > > > > > > > > I have traced the behaviour to the following combination of > > > > > > > > > > circumstances: > > > > > - BusyBox ntpd is configured to start at boot > > > > > - Interface eth1 is *not* present > > > > > > > > > > - In my case because the required natsemi module is not in > > > > > the > > > > > > > > > > default initrd.lrp > > > > > > > > > > - Dnsmasq has resolv-file=/etc/resolv.conf > > > > > > > > > > I can remove the delay by changing/correcting any one of those. > > > > > > > > > > As you know, my preference is to change the default setting of > > > > > resolv-file for dnsmasq (to /etc/dhcpc/resolv.conf) because that is > > > > > what many users will want anyway, and we do include dhcpcd.lrp in > > > > > the default LRP= in the disk images so we implicitly assume use of > > > > > DHCP on eth0... > > > > > > > > Can be done. But this will solve the issue for those using dhcpc, but > > > > not for those connecting via pppoe. So the more generic solution > > > > would be to disable ntpd start by default. > > > > > > > > I do not have any preference here, whatever we do it requires some > > > > configuration b ythe user and some documentation :) > > > > > > > > kp > > > > > > Agreed; we cannot please all of the users all of the time... > > > > > > IMHO, most users will want ntp working. If we disable it we need to > > > make it easy to re-enable, and right now BusyBox ntp is not > > > configurable from the leafcfg menu. > > > > > > What about creating a pseudo-package for BusyBox ntp (bbntpd.lrp or > > > something) which contains the configuration files? The "executable" > > > would remain part of the base install. If we do that and omit it from > > > the LRP= setting it will not be loaded at first boot. > > > > Good idea; > > > > I've created a pseudo packackage with the config files. > > Hi kp, > > Cool. Thanks for doing that. > > > If that is installed, configuration of /etc/default/ntpd is possible > > through lrcfg, - so we may set NTPDRUN=no, install it by default and let > > the user re- enable it... > > > > kp > > ...or we leave NTPDRUN=yes and do *not* install it by default so the > user just has to add to leaf.cfg. > > I am happy either way so your choice. I use ntpd.lrp myself anyway :-)
Ok, will do it my way :) Changing the config is slightly easier than editing leaf.cfg - it just seems more "natural" to me. I use bb ntpd, if that adds some more weight :) kp ------------------------------------------------------------------------------ What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
