Bug#774584: rtpproxy: Deamon does not start as init script points to wrong executable path

[Raphael Michel]

Package: rtpproxy
Version: 1.2.1-1
Severity: grave

Dear Maintainer, 

on my system, rtpproxy does not start. I believe the reason is that the
init script contains

DAEMON=/usr/sbin/$NAME

but the binary only exists in /usr/bin. Changing this line in the init
script to

DAEMON=/usr/bin/$NAME

makes the deamon work on my system.

Best regards,
Raphael

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rtpproxy depends on:
ii  adduser  3.113+nmu3
ii  libc6    2.19-13

rtpproxy recommends no packages.

Versions of packages rtpproxy suggests:
pn  ser | openser  <none>

-- Configuration Files:
/etc/default/rtpproxy changed [not included]
/etc/init.d/rtpproxy changed [not included]

-- no debconf information
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: Digitale Signatur von OpenPGP
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20150104/9d380b99/attachment.sig>