Including Mnesia in a supervision tree?

[Vance Shipley]

Shawn,

You can specify the start type of an application as well:

         {mnesia, "4.1.6", permanent},

If left out it defaults to temporary.  Possible choices are;
permanent, transient or temporary.

   If a temporary application terminates, this is reported 
   but  no other applications are terminated.

   If a transient application terminates with Reason =  normal, 
   this is reported but no other applications are  terminated. 
   If a transient application terminates abnormally,  all other 
   applications and the entire Erlang node are also  terminated.

   If a permanent application terminates, all other  applications 
   and the entire Erlang node are also terminated.


	-Vance

On Sat, Feb 07, 2004 at 03:36:33PM -0500, Shawn Pearce wrote:
}  Thanks for the reply Vance, as I'm also going to be looking at
}  the release stuff yet.
}  
}  How does this help me when Mnesia fails?  Does the release handler
}  above the applications then restart the applications, or is the
}  node considered "dead" and restarted by heart?
}  
}  I'm not looking for Mnesia to fail, just wondering how it fits into the
}  otherwise nice failure handling that OTP provides.
}  
}  Vance Shipley <vances@REDACTED> wrote:
}  > Shawn,
}  > 
}  > You should create a release.  Create a release resource file
}  > like in this example file named myrelease.rel:
}  > 
}  >    {release, {"releasename", "0.1"}, {erts, "5.3.1"},
}  >         [{kernel, "2.9.2"},
}  >         {stdlib, "1.12.3"},
}  >         {sasl, "1.10"},
}  >         {mnesia, "4.1.6"},
}  >         {eva, "2.0.4"},
}  >         {myapp, "0.1"}]}.
}  
}  -- 
}  Shawn.