Logging startup of the first instance...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2012/6/4 David Henningsson <david.henningsson at canonical.com>:
> 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? Or would it be possible to add some kind
> of expansion to the log file name to make the files unique?

Hi David,

I'm doing the GSoC to enhance the logging functionality in pulseaudio,
I could take a look at this issue and try to improve it a little bit.
:)


[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux