Hi Brandon, This is an interesting issue. I don't understand what could be going on. Even if you remove the log file, it shouldn't crash liquidsoap (like all Unix programs, it would keep writing in the file, even though the file has become inaccessible to anybody else) and even if it crashed, it should always tell you why in the logs -- even though sometimes it's not in the last few lines, but may be 20-30 lines before the end.
It might be a very hard crash, or a problem in the lower levels of liquidsoap (a segfault, or maybe the dtools library...) but that's just wild guessing. Does your log end cleanly with a STOP line? One thing that could help, if that's possible: run liquidsoap in a terminal, which is the simplest way to make sure that you see all information: stdout, stderr (even though they should normally be piped to the logs) and the error code. Cheers, -- David ------------------------------------------------------------------------------ Malware Security Report: Protecting Your Business, Customers, and the Bottom Line. Protect your business and customers by understanding the threat from malware and how it can impact your online business. http://www.accelacomm.com/jaw/sfnl/114/51427462/ _______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
