From 9f23c8f36299635f78475ee9e90b0a20c5cf3b84 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Sun, 21 Nov 2004 22:07:47 +0000 Subject: Documentation updates git-svn-id: file:///home/lennart/svn/public/pulseaudio/trunk@310 fefdeb5f-60dc-0310-8127-8f9354f1896f --- doc/FAQ.html.in | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'doc/FAQ.html.in') diff --git a/doc/FAQ.html.in b/doc/FAQ.html.in index 751ef562..9cacfb4c 100644 --- a/doc/FAQ.html.in +++ b/doc/FAQ.html.in @@ -126,9 +126,11 @@ connect to a running polypaudio daemon try using the following commands:

killall -USR2 polypaudio
 bidilink unix-client:/tmp/polypaudio/cli
-

BTW: Someone should package that great tool for Debian!

+

BTW: Someone should package that great tool for Debian!

+

New: There's now a tool pacmd that automates sending SIGUSR2 to the daemon and running a bidilink like tool for you.

+

  • How do the polypaudio libraries decide where to connect to?

    The following rule applies:

    @@ -142,10 +144,11 @@ bidilink unix-client:/tmp/polypaudio/cli
  • If $DISPLAY is set, the library tries to connect to the default TCP port of that host. If the connection fails, it proceeds with the next item.
  • The connection fails.
    • -

    - +

  • Why the heck does libpolyp link against libX11?

    +

    The Polypaudio client libraries look for some X11 root window properties for the credentials of the Polypaudio server to access. You may compile Polypaudio without X11 for disabling this.

    • +
    -- cgit