Elizabeth Dodd wrote: > On Fri, 30 Jan 2009, Duncan Webb wrote: >>> while it is not in use now, nothing happened. >>> I watched top carefully and mplayer died so fast I didn't usually see it >>> appear. >> This where DEBUG_CHILDAPP comes in handy as it saves the output of >> mplayer to a pair of log files, you can then examine the log files and >> see what the error is. > > nothing whatsoever logged > looked there > the logs ere empty > debug levels set to 1
DEBUG_CHILDAPP enables the spawned processes to create 2 log files which should be named something like: mplayer-stdout*, mplayer-stderr*. I don't think it depends on DEBUG but you can add: LOGGING = logging.DEBUG LOGGING_RECORDSERVER = logging.DEBUG DEBUG_CHILDAPP = 1 DEBUG = 1 The logging bit is important for debug messages but should not affect logging from child applications. Duncan ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
