#609724 [trickle] Please supply a trickled init script

Package:
trickle
Source:
trickle
Description:
user-space bandwidth shaper
Submitter:
Lars Kruse
Date:
2015-01-07 19:03:10 UTC
Severity:
wishlist
#609724#5
Date:
2011-01-11 22:34:26 UTC
From:
To:
--- Please enter the report below this line. ---

Hi,

some users may consider it beneficial to have a prepared init script for
running the trickle daemon on startup.
Personally I would even like a ready-to-use init script to be installed by
default, but currently there seem to exist two issues with the current trickle
package blocking this approach:

1) trickled should not run as user root - thus a (currently
non-existing) "trickled" user would be necessary.

2) trickle(d)'s default socket location is /tmp/.trickled.sock. This is (as
far as I understand it) not in line with the debian policy. It should probably
be placed below /var/run.


Thus maybe it would be just as helpful to provide a sample init script for
everyone who needs to run trickled permanently.
Attached you find an init script and the accompanying /etc/default/trickle file
that could be used together as a clean startup solution for trickled.
I would really appreciate it, if the trickle package would supply these two
files as examples in its doc directory.
What do you think about it?

thanks for your time,
Lars


Debian Release: 6.0
  990 testing         localhost
--- Package information. ---
Depends                     (Version) | Installed
=====================================-+-===================
libbsd0                      (>= 0.0) | 0.2.0-1
libc6                        (>= 2.3) | 2.11.2-7
libevent-1.4-2     (>= 1.4.11-stable) | 1.4.13-stable-1


Package's Recommends field is empty.

Package's Suggests field is empty.

#609724#10
Date:
2015-01-07 19:00:40 UTC
From:
To:
Dear Maintainer,

I've created and have been using the attached init-script with the corresponding config file for a while with success.

Not sure if it can be added to the package, but at least they could be added to an "examples" directory under the package's doc one.

Regards,