Thank's for your input, my first option was to have a process
doing wait and checks, but I would be glad if I can avoid it,
just as you say.
These advices (or hint/tips) is for the moment above my knowledge.
Have to read some manuals here.

The use of vmur was to be able to communicate even when network is down.
The trick here is to have the 'failing' server to DETatch the disk.

For now this seams like a 'brainer'  ;)

___________________________________________
Tore Agblad
Volvo Information Technology
Infrastructure Mainframe Design & Development, Linux servers
Dept 4352  DA1S 
SE-405 08, Gothenburg  Sweden

Telephone: +46-31-3233569
E-mail: [email protected]

http://www.volvo.com/volvoit/global/en-gb/

-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Rob van 
der Heij
Sent: den 9 september 2010 11:38
To: [email protected]
Subject: Re: vmur usage ?

On Thu, Sep 9, 2010 at 10:49 AM, Martin Schwidefsky
<[email protected]> wrote:

> Something like this?
>
> commit 1ffaa640c6ba135aafc91841204e41846eae6841
> Author: Hendrik Brueckner <[email protected]>
> Date:   Mon Mar 8 12:26:26 2010 +0100
>
>    [S390] smsgiucv_app: deliver z/VM CP special messages (SMSG) as uevents
>
>    The smsgiucv_app driver registers a callback with the smsgiucv driver
>    to receive z/VM CP special messages (SMSG) starting with "APP".
>
>    When the callback is called for special messages, the driver creates
>    an uevent for the received message.  The uevent consists of additional
>    environment data containing the message prefix ("APP"), message sender,
>    and message content.

Yes, neat.  My humble apologies, it must have gone straight through my
head. And I assume it just refers to SMSG since that's the one they
told you about, but actually takes anything that gets delivered
through *MSG (and passes the message type along) ?

For most of us it would also be nice to hear from Mark and Shawn when
it will be in their favorite distro.

| Rob

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to