Here's one possibility: I have a number of IP addresses bound to the server's NIC, but LMS is run on only one of them. Could be that the installer is checking for port conflicts - something that probably requires waiting for a timeout - on every IP address on the machine. If that's it, it seems odd that the installer would start the service before finishing this check.
This might come close. While I'm not sure which addresses it is checking (all or the first only - I'm ooto right now), it does check whether the ports are reachable once the service has started. So yes, if it happen to pick all of them, or only one (being the wrong one), it might indeed run quite a few tests running into timeouts. If this is bothering you then I'd seriously recommend using a different update uproach. The tool to uncompress files from the installer might do the job you want in a fraction of the time. -- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
