Alberto Hernando wrote: > El Thursday 23 August 2007 19:49:51 Duncan Webb escribió: >> What does /tmp/roms contain, reasonable data or junk? >> >>> The same roms don't generate any error in freevo 1.6.2. Any idea? I have >>> no clue about this log. >> Not a big games player but I do have a couple of roms and it doesn't >> crash when entering a mame menu, Have you run out of disk space in /tmp >> or is the /tmp/roms not readable? > > Hi. > > I've found what happened... more or less. > > First, the freevo user has full access to /tmp, but /tmp/roms simply never > exists. And /tmp is never full either. > Second, I don't start mame with /usr/bin/xmame.x11 or similar. I have my own > script to call it, located in /home/freevo/bin/mame. Inside I call xmame.x11, > of course, but I do it like this so that I can add more options, and other > things I need to do before and after playing a game. It's the same that I > have in freevo-1.6.2 with no problem. > What happens then? As I said, I have two freevo in the same box. At first, I > was sharing the cache. But every time I boot one after the other, the cache > was recreated. I guess the system must be different. So I decided to use > different cache directories. And then mame started crashing. The first time > mame is run, it creates a cache, not of the roms you have, but the ones it > can use. Under freevo-1.6.2 and the script, there is no problem, the cache > can be built. But under 1.7.3, it crashes. If I use the same cache directory > for both freevos, no problem, the mame cache from 1.6.2 works for 1.7.2 and > mame runs. So 1.7.2 can run mame with my script, but can't build the cache. I > thing it has do with something about that freevo can't find the config files > of my script (there aren't!) and that's why it crashes. > If you thing this is a serious bug, I can reproduce it whenever I want and I > can give you more info, if you need it.
I'm not really sure exactly what the problem is but I think that /tmp/roms is hard-coded into freevo so if you have moved it I would expect a crash. The contents of /tmp/roms is created by xmame with xmame.xll -listxml -out /tmp/roms. Actually nothing has changed in the xmame code for a very long time. This doesn't help solve your problem much but try executing: /path/to/your/script -listxml -out /tmp/roms and see if /tmp/roms is created correctly. Duncan ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Freevo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-users
