Team Did I mention that this is a non issue if you do not use the default "xen fudge script" and setup the bridges manually????
Helllo, hello, is this microphone on... can anyone hear me... hello hello :-) On Tue, 2009-11-03 at 16:50 -0500, Madison Kelly wrote: > Steven Dake wrote: > > Your right - xen shouldn't be mucking with all these network config > > options in the s99 run position. > > > > Unfortunately this problem was detected after most distros released the > > cluster stack + xen software. A majority of distros policy is that > > start and stop positions for init scripts may not change during the > > major version of the product life. (IE no init script changes to RHEL5 > > for example). > > > > This is why other hacky workarounds were created which work to varying > > degrees. > > > > Hope that helps > > -steve > > That would explain why the Red Hat bug fix revolved around the cman > detecting the existence of Xen and firing it's config scripts before > processing itself. However, it's trying to detect Xen's existence by > checking for default values that users and programs can change. *sigh*. > > Anywho, thanks again! > > Madi > _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
