Pulse audio and NFS home directories.

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

 



On Fri, 08.05.09 11:46, mike _ (arizonagroovejet at gmail.com) wrote:

> -rw------- 1 xxxxx xx 3.1M 2009-05-08 08:52
> 7c163669fa3688bf66ba6ccd49ef3bce:device-volumes.i686-suse-linux-gnu.gdbm
> -rw------- 1 xxxxx xx 3.0M 2009-05-08 08:52
> 7c163669fa3688bf66ba6ccd49ef3bce:stream-volumes.i686-suse-linux-gnu.gdbm

> Is anyone able to offer an explanation and/or solution for why the
> file sizes are so large on NFS, and/or why pulseaudio chocks when
> ~/.pulse is a symbolic link?

PA uses those to gdbm files to save/restore information like
volume/mute/device for all streams and devices. Is it possible that
simply because your NFS home directories are used across more machines
mroe data ends up being stored in those gdbm files?

To check how much and which data is actually stored in those files try
something like this:

python <<EOF
import gdbm
f = gdbm.open("7c163669fa3688bf66ba6ccd49ef3bce:device-volumes.i686-suse-linux-gnu.gdbm", "r")
k = f.firstkey()
while k != None:
    k = f.nextkey(k)
    print k
EOF

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4



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

  Powered by Linux