On 09.01.2024 13:33, Roger Pau Monné wrote: > On Tue, Jan 09, 2024 at 11:58:48AM +0100, Jan Beulich wrote: >> Plus the call isn't pointless even in >> release builds, because of the log messages issued: Them appearing >> twice in close succession might be a good hint of something fishy >> going on. > > Why do you mention the messages appearing twice? Won't the first > check call return error and thus should prevent the caller from > attempting to load the state?
Well, what exactly is going to be the reason for a failure on the "real" invocation when the "dry-run" one supposedly failed is unknown. But you're right, messages occurring twice indeed may not be very likely. It's more like these messages appearing and then loading still continuing which might make obvious that something went wrong. Jan
