summaryrefslogtreecommitdiffstats
path: root/src/pulsecore/svolume_arm.c
diff options
context:
space:
mode:
authorNix <nix@esperi.org.uk>2009-09-26 20:18:00 +0100
committerLennart Poettering <lennart@poettering.net>2009-09-29 19:32:25 +0200
commiteac566226ed9026347cdb415a93ad9b15fbd8b45 (patch)
tree40f1d8ab92b4c0dce2da8fc698faf0c5421bab5d /src/pulsecore/svolume_arm.c
parentfaf113d95bfa6be3baa5d5a7330984e04bfd895f (diff)
Don't refuse to start on systems using GNU stow, graft, STORE et al
There are multiple package management systems out there which implement packages using symlinks. The recent (otherwise useful) check to ensure that a re-executed pulseaudio is actually reexecuting itself unfortunately breaks in the presence of all these packaging systems, because PA_BINARY refers to its installed location (e.g. /usr/local/bin/pulseaudio), which is a symlink to the binary (e.g. /usr/local/stow/pulseaudio-0.9.18/bin/pulseaudio), because /proc/self/exe always contains the canonical path of the executable, with all symlinks resolved. (At least one distribution uses a symlink-based packaging system, so will be forced to apply this locally in any case.) The fix is simple: canonicalize PA_BINARY before equality-testing. (This should be completely safe, because the OS does just that when PA_BINARY is executed.) The patch is against 0.9.18, but applies without fuzz to current master.
Diffstat (limited to 'src/pulsecore/svolume_arm.c')
0 files changed, 0 insertions, 0 deletions