On mer, 2005-04-20 at 22:51 +0200, Lars Marowsky-Bree wrote: > On 2005-04-20T22:39:56, christophe varoqui <christophe.varoqui@xxxxxxx> wrote: > > > Multipathd *never* decides to change a map. All it does is exec > > multipath, which means two runs of multipath gave 2 differents maps : > > very bad, but nothing to do with code divergence between daemon and > > tool. > > But it _always_ happens when multipath is called from multipathd. > > It _never_ happens when multipath is called manually by root. > > It didn't with -pre14, but does with -pre16. > > What could have caused this? > Don't forget the binaries caching in a ramfs. If you don't restart the daemon, it may still use a WIP multipath version as a callout. I'll try and reproduce this at OSDL. regards, -- christophe varoqui <christophe.varoqui@xxxxxxx>
