Being logged in to a box remotely and using up2date to upgrade the box, the
upgrade of xinetd causes the up2date connection to be lost and the upgrade
to not finish.
I don't see how that is possible, as up2date doesn't use xinetd at all. Adrian?
(just to clarify, so glen doesn't put this on the must-fix list: The report is
I cant think of any connection between xinetd and up2date.
It doesnt start anything from xinetd, or depend on anything
typically launched from xinetd. Coincince, I suspect.
Derek, if you can reproduce it, you can re-open it.
If so, more info must be added so we can find out what is the problem - I can't
see any way it could possibly be xinetd.