Comment 23 for bug 129081

> First of all, I would like to see the package in revu:

That will be my next step on this subject.

> Concerning the daemon initialisation, you should refer to the debian policy:
>
> http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit
> http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.4
>
> The scripts in /etc/init.d should be good examples of how to write the init
> script.
>
> The dmraid package should give you an idea how to install and start it
> (basically, its just a question of installing the script in /etc/init.d and
> registering it with update-rc.d during postinst, which is done calling the
> dh_installinit debhelper)
>

I will take a look at the policy and the dmraid example, do you know
about /etc/init.d/skeleton, I used to write one or two init.d script
based on it.

> Concerning the locations, again the policy is the best available source:
>
> http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1
> http://www.debian.org/doc/debian-policy/ch-files.html
>
> As you already correctly said:
>
> configuration files go to /etc/mumble
> log files in /var/log/mumble (there should be a configure option)
> pid files in /var/run/mumble (there should be a configure option)
> pl files in /usr/lib/cgi-bin/mumble
>
> I don't think /var/lib is a good place for murmur.sqlite, shouldn't be
> in /etc/ too?
>

/var/log/mumble/mumble.log vs /var/log/mumble.log
/var/run/mumble/mumble.pid vs /var/run/mumble.pid
/usr/lib/cgi-bin/mumble.pl vs /usr/lib/cgi-bin/mumble.pl

What do you think ?