[erlang-questions] Mnesia supervisor restart strategy...

Edwin Fine <>
Sun Sep 28 18:12:35 CEST 2008


My understanding is that you can specify options for an application as

   - On the command line as -MyAppName key value
   - In the config file as {MyAppName, [{key, value}]}
   - In the .app file

The command line overrides the config file settings, which override the app
file settings.

On the command line, writing -mnesia foo bar simply inserts the key/value
pair {foo, bar} into the application environment for mnesia. I expect (but
am no expert) that you shoud be able to put the values in the config file
just as you can for sasl and any other app.

            {sasl_error_logger, {file, "/tmp/foo.sasl_log"}}
            {dir, "/my/mnesia/dir"}

It's worth a try anyway.


On Sun, Sep 28, 2008 at 7:04 AM, Dan Rubino <>wrote:

> Hi all,
> I have setup a release as suggested whilst specifying Mnesia in the list
> of required apps. This starts Mnesia automatically which is perfect.
> Now when I look at mnesia through the appmon, I see it has a supervisor
> attached to it - great. My question now is of course, am I able to
> specify the restart strategy for it? Can I see the settings it is
> currently running under perhaps (just so I can understand its
> behaviour)?
> Also, is there another way within a release to specify the directory of
> the Mnesia instance? So what I am saying is I currently use the
> commandline option -mnesia dir '"/path/to/mnesia/instance"'
> Is there another way to specify this in config perhaps?
> Many Thanks,
> Dan
> _______________________________________________
> erlang-questions mailing list
> http://www.erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20080928/97cac8e9/attachment.html>

More information about the erlang-questions mailing list