>because the startup script is writing its startup debug messages to stdout
>and not a log file. I like this feature because, in development, it allows
>me to test certain MX features in my browser and then toggle over and see
>any error messages that result from it. In particular, I've found that if
>I'm having trouble connecting to a datasource, the debug out in the console
>is more informative that what the MX Administrator is telling me (i.e., bad
>username/password, TNS problem, etc.).
>
>All you have to do is hit enter a couple of times and you'll get a command
>prompt and you can continue on. Hitting Ctrl-C is the equivalent of killing
>the process, which is why your MX instance dies.
>
One last thing to point out that I just realized after re-reading your post.
To start up your MX instance as a background process that doesn't die when
you exit the console, use this:
./jrun -nohup start [instance name]
The -nohup is in the docs, but I don't ever see people refer to it in their
posts on the subject. -nohup signals the kernel to start the process as a
background process.
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
