A Mennucc wrote: > hi, > > someone just mentioned 'print' statements used for debugging: > those should be avoided as much as possible in final releases. > > Some time ago, I did restart one of the freevo servers using > a ssh terminal. After some time I noticed that it had crashed. > The reason is that, once the ssh connection is shut down, > then the stdout is closed, and any 'print' will throw > an exception.
Here are some tips. --daemon should prevent a server process from dying when an shell have been killed. The idea is that the process is forked and then belongs to the init process. Normally stdout and stderr should go to a log, this happens in Freevo but they still write to the console. Not sure what happens in this case, something to test? screen is a useful tool in these cases. Also set the logging level to CRITICAL. > So I recommend that all 'print' be commented out in the > final 1.8.4 release Do this as a matter of course. I mark mine with DJW so I can grep the source for these (but sometimes forget) Duncan ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
