| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | DMAPI implementation about undeliverable event messages |
| From: | Aurelien Degremont - Stagiaire <degremont@xxxxxxxxxxx> |
| Date: | Mon, 07 Mar 2005 10:03:46 +0100 |
| In-reply-to: | <9b3ffd852cd198d4c349e2606122e4@trevor> |
| References: | <9b3ffd852cd198d4c349e2606122e4@trevor> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.6) Gecko/20040113 |
Hello, I just wanted to know how the SGI DMAPI implementation reacts when it must throw a synchronous event message when no process exists to receive it (but was registered before, no longer available know, application has died by example). It looks like the requesting process is blocked. Correct? If yes, does a solution to unblocked it exist? Or is it blocked forever?
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: oops when calling dm_set_disp(), Damian Hazen |
|---|---|
| Next by Date: | Re: DMAPI implementation about undeliverable event messages, Dean Roehrich |
| Previous by Thread: | Re: TAKE 925910 - fix xfs_freeze, Greg Freemyer |
| Next by Thread: | Re: DMAPI implementation about undeliverable event messages, Dean Roehrich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |