On Mon, 2012-06-04 at 15:04 +0200, David Henningsson wrote: > Sometimes I have users who complain about some problem, but after a > "pulseaudio -k" the problem is gone. Therefore asking them to restart > pulseaudio with -vvvv switch will not give any information about the error. > > * I could log to syslog (the default), but once I enable debug level > log, the syslog daemon can start to ratelimit, especially during the > startup phase of pulseaudio. > > * I could log to file, but then that file would quickly get > overwritten, as soon as pulseaudio restarts. > > Is there a trick I'm missing here? None that I know of. I've seen an approach where the log file name with timestamp is generated by the init script (system-wide mode was used), but that's probably not always doable (generating the timestamp when autospawning would probably be impossible). > Or would it be possible to add some > kind of expansion to the log file name to make the files unique? Sounds fine to me. -- Tanu
