I wrote: > Now the problem is that it appears to hang when trying to load the > config file (or shortly thereafter), and the MVP perpetually shows the > screen with the www.mvpmc.org logo.
As I was revising the wiki page on the command line options, I was wondering if there was a recommended procedure for debugging config file problems? (One recommendation should be to try out the commands first via telnet.) Are the messages (presumably written to STDERR) output by mvpmc when it is started with invalid command line options from a config file logged anywhere? Or in other words, is STDERR redirected to a file when the dongle.bin.config script is executed? If not, should the example dongle.bin.config scripts[1] include commands to accomplish that as a recommended practice? 1. http://mvpmc.wikispaces.com/mvpmc.config I see that page also documents what I observed: > Common Problems > error in this file can cause the mvp to hang on the www.mvpmc.org > splash screen (v0.3.3) Any chance the GUI could display the error information, or at least a generic message saying to check the error logs, rather than just showing the www.mvpmc.org logo? I'm guessing the logo is probably shown by some script copying a bitmap to a frame buffer, or something like that (seeing as it happens before mvpmc loads). Perhaps the script that launches dongle.bin.config could check for an error exit code and copy a bitmap with an error message to the screen? -Tom ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mvpmc-users mailing list Mvpmc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
