[Mono-list] A Problem with XSP

Filip Bri brcha@users.sourceforge.net
Tue, 24 Feb 2004 13:34:07 +0100


--=-6ewbTkAvDmP201M28wXC
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On Tue, 2004-02-24 at 11:57, Jörg Rosenkranz wrote: 

> The shared handles storage in ~/.wapi seems to be still a bit unstable. 
> Is there any way to detect and repair a corrupted .wapi directory 
> instead of raising the "Shared memory sanity check failed." message?
> 
> We're deleting it in the start script of our application, but that
> works only because that's the only Mono app running in this user
> context.

Well, I guess that there could be a way to detect and repair the
corrupted .wapi directory. Instead of raising the "Shared memory sanity
check failed." message in ${MONO_SOURCE_DIR}/mono/io-handles/shared.c
you should remove the ~/.wapi directory and rerun the shm_file_attach
function. But I would leave that to Mono developers because I don't know
what consequences could that have, so it would be better if they could
think that over and "repare" the mono/io-handles/shared.c file.
I don't know what is the way to corrupt the ~/.wapi directory. In my
case, it was the system crash, and since the mono application was
running, that file was open and obviously it was not saved the right way
:) If that is the only way, you could edit init scripts and remove that
(or those) directories at boot time. If there are other ways to corrupt
the ~/.wapi, then only editing mono/io-handles/shared.c is the right
way.

-- 
Filip Brcic <brcha@users.sourceforge.net>
WWWeb:  serbianc.sourceforge.net
Jabber: brcha@elitesecurity.org
ICQ#    40994923

--=-6ewbTkAvDmP201M28wXC
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.0.8">
</HEAD>
<BODY>
On Tue, 2004-02-24 at 11:57, J&#246;rg Rosenkranz wrote:<FONT COLOR="#737373"><I> 
<BLOCKQUOTE TYPE=CITE>
<PRE>The shared handles storage in ~/.wapi seems to be still a bit unstable. 
Is there any way to detect and repair a corrupted .wapi directory 
instead of raising the &quot;Shared memory sanity check failed.&quot; message?

We're deleting it in the start script of our application, but that
works only because that's the only Mono app running in this user
context.</I></FONT></PRE>
</BLOCKQUOTE>
Well, I guess that there could be a way to detect and repair the corrupted .wapi directory. Instead of raising the &quot;Shared memory sanity check failed.&quot; message in ${MONO_SOURCE_DIR}/mono/io-handles/shared.c you should remove the ~/.wapi directory and rerun the shm_file_attach function. But I would leave that to Mono developers because I don't know what consequences could that have, so it would be better if they could think that over and &quot;repare&quot; the mono/io-handles/shared.c file.<BR>
I don't know what is the way to corrupt the ~/.wapi directory. In my case, it was the system crash, and since the mono application was running, that file was open and obviously it was not saved the right way :) If that is the only way, you could edit init scripts and remove that (or those) directories at boot time. If there are other ways to corrupt the ~/.wapi, then only editing mono/io-handles/shared.c is the right way.
<PRE><TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<PRE>-- 
Filip Brcic &lt;brcha@users.sourceforge.net&gt;
WWWeb:  serbianc.sourceforge.net
Jabber: brcha@elitesecurity.org
ICQ#    40994923</PRE>
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>

--=-6ewbTkAvDmP201M28wXC--