Bug#388037: Separate client binary or add START_DAEMON option to /etc/default/stun

[Christian Hammers]

Package: stun
Version: 0.96.dfsg-1
Severity: normal

Hello

We're only using the stun client binary on one system to use it for
monitoring purposes. When installing it we ran into two problems:

a) The package seems uninstallable without modifications:
	Setting up stun (0.96.dfsg-1) ...
	No primary IP given. Exiting.
	invoke-rc.d: initscript stun, action "start" failed.
	dpkg: error processing stun (--configure):
	subprocess post-installation script returned error exit status 1
   I would consider this a bug, every package should be installable
   without error messages. Could be solved by the solution proposed for
   b), too.

b) As we only need the client-binary and splitting client and server
   would probably be overkill something like the following would be
   good in /etc/defaults/stun
	# Change this from /bin/true to /usr/sbin/stun enables the Server
	DAEMON=/bin/true

bye,

-christian-

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.17.6-fc4-westend2
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE)

Versions of packages stun depends on:
ii  libc6                 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an
ii  libstdc++2.10-glibc2. 1:2.95.4-22        The GNU stdc++ library

-- no debconf information