Mnesia question

[Chandrashekhar Mullaparthi]

The error message basically is that the module trex_sh is not loaded. Check
that the module is loaded. Here is an example checking that the kernel
module is loaded.

1> m(kernel).
Module kernel compiled: Date: April 12 2002, Time: 05.57
Compiler options:  [v3,
                    debug_info,
                    {i,"/clearcase/otp/erts/lib/kernel/src/../include"},
                    {outdir,"/clearcase/otp/erts/lib/kernel/src/../ebin"},
                    {cwd,'/clearcase/otp/erts/lib/kernel/src'}]
Object file: D:\PROGRA~1\ERL51~1.1/lib/kernel-2.7.2/ebin/kernel.beam
Exports: 
         config_change/3
         init/1
         module_info/0
         module_info/1
         start/2
         stop/1
ok
2> 


cheers
Chandru

-----Original Message-----
From: Carlos Silva [mailto:carlos@REDACTED]
Sent: 06 December 2002 17:13
To: erlang-questions@REDACTED
Subject: Mnesia question


Hello I've just arrived to the "Erlang world" and I've been trying to
introduce myself in Mnesia DBMS.
 
I found a tool to give the user graphical access to the mnesia and ets
tables, called "trex-2.6.tgz - Leif Lorentzen, ", under the "User
Contributions" page. 

But I have some troubles in using it. The message that I receive from my
erlang shell is the following.

4> trex:start().
<0.124.0>
*** Could not start trex_sh! Reason:
{badrpc,{'EXIT',{undef,[{trex_sh,start,[]},
{rpc,call,4},{trex,start1,2}]}}}

I'm not ready to understand it yet and I will apreciate any help you could
give me about this (the answer or to whom I could contact to answer my
questions). May I copy the files in another directory? Run something else
before trex? etc.

Thank you very much, Carlos.-



NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.