On Wed, Mar 14, 2012 at 01:47:12PM -0700, Steve Sundstrom wrote: > > So what happens when you check that the network is reachable before you > > execute the operation, and then a network failure happens later during > > the operation? You've just moved the point of failure without actually > > improving the user experience. > > I agree that is a possible scenario, but as far as network > intermittency is concerned, probably in the 0.01% range of occurrence, > if not less. The other 99.99% of the time we would discover the > problem before firing a doomed install request at a dead or > unreachable address. In the case you describe, we would figure out > that the network *became* unreachable checking the error as you > suggest.
I don't understand your use case. If the publisher is unreachable, pkg already exits gracefully with a "Network Unreachable" message. What problem are you actually trying to solve? More than that, I'm not convinced that a network unreachable error implies publisher misconfiguration. More likely than not, you have a routing problem that needs to be fixed. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
