Bug 58389 - Improve the "set log target" functionality
Summary: Improve the "set log target" functionality
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: clients (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
Keywords: love
Depends on:
Reported: 2012-12-17 05:28 UTC by Tanu Kaskinen
Modified: 2018-07-30 09:56 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Tanu Kaskinen 2012-12-17 05:28:39 UTC
The "set log target" operation is supported only by pacmd. The functionality should be added to pactl too (and therefore to the client interface). Also, currently the "newfile" target is only supported when it's given as a command line parameter to the daemon or in daemon.conf. The target parsing should be centralized in pulsecore/log.c, so that all targets will always be availble with all interfaces (command line, daemon.conf, pacmd, pactl).
Comment 1 Tanu Kaskinen 2013-04-21 11:45:26 UTC
A note about security: setting a new target, especially a file target, should probably be prohibited by default in all other cases except when running in the per-user mode and the client is running under the same user as the server. This is not currently a problem, because pacmd doesn't work remotely nor in the system mode, but if the functionality is added to pactl too, it makes it possible for anyone who has access the pulseaudio server to write (and overwrite) files anywhere where the pulseaudio process has write access.
Comment 2 GitLab Migration User 2018-07-30 09:56:46 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/133.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.