On Fri, April 9, 2010 8:27 am, Anders Eriksson wrote: > > ehi...@gmail.com said: >> Off the top of my head it looks like the recordserver is just plain >> failing >> shortly after it is started. Have you checked the logs for teh >> recordserver? >> >> Evan > Yep. The logs indicate that it's there (no indication of it closing down). > Ps > reports that the fingered pid is still alive and kicking. > > How do people normally pull this off? I'm looking at having the *servers > started by the normal init.d scripts and the freevo GUI process as a > dedicated > user (started from inittab). I'm had that (sort of) working on an old > machine, > but when setting up a new one I discovered that the init.d start/stop > actions > didn't work as expected. >
The way I've done it is to start the record server on one of the ttys using inittab this has several advantages for me. I can see any error messages that get output and I can use 'freevo recordserver --stop' to restart the recordserver (init automatically restarts it when it dies) if I want to change anything. On my frontend I use gdm to automatically log in to my freevo user and then put the things required to start freevo in .xsession. I had been using rc.local to start freevo but the gdm way is much prettier as I know don't get the startup messages output just a flashy splash screen, better WAF :-) . good luck Adam ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
