On 2006-05-25T11:15:57, [email protected] wrote:
> linux-ha CVS committal
>
> Author : lars
> Host :
> Project : linux-ha
> Module : resources
>
> Dir : linux-ha/resources/OCF
>
>
> Modified Files:
> Filesystem.in
>
>
> Log Message:
> - In post-notify for a stop, the "start" list should be empty and
> ignored.
In start/stop notifications, the stop/start list should be empty
respectively, no? (As the stop can only be scheduled after the start has
completed and vice-versa, which includes the notifications, I hope.)
But it is not:
notify: post for stop
notify active: xen-4 xen-3 xen-1
notify stop: xen-2
notify start: xen-4 xen-3 xen-2 xen-1
Even though obviously no start is forthcoming. (xen-2 is down,
afterall.)
I worked around this in the Filesystem RA now, but it is somewhat
confusing.
Sincerely,
Lars Marowsky-Brée
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
