Re: RFC: Project geom-events

On 05.10.2011 10:39, Lev Serebryakov wrote:
>>    (1) Class and name of GEOM which is affected.
>>    (2) Name of provider which is affected.
>>    (3) Name of underlying provider which is lost (consumer from
>>        reporting GEOM's point of view).
>>    (4) Resulting state of affected provider (fixable, alive, dead).

All except last could be get from the consumer in the orphan method.

>   And, I'm affraid, that geom_dev could not distinguish manual
> operations with geom (performed from userland by administrator) and
> real accidents. I don't want geoms to post DISCONNECTED or DESTROYED
> events when administrator knows what he does -- and it could lead to
> race conditions, when administrator rebuild array and forgot todisable
> spare drives, for example.
>   Other example -- geom_label creates and destroys about 10 labels on
> boot (on my test VM) and, if DESTROYED will be reported by very
> generic mechanism, it will end up with 10 e-mails to administrator on
> every boot -- I've got this, when put notifications in too generic
> place for first try.

Ok, good point. Can you explain how your script will distinguish which
actions are performed by administrator? Since change made by administrator
could trigger disappearing of several child geoms.

-- 
WBR, Andrey V. Elsukov