stunnel not started by default
Bug #373487 reported by
Justin Dugger
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| stunnel4 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: stunnel4
stunnel4 init scripts ship with ENABLED=0, which causes the thing not to run. This is a problem:
* Firstly, it's not obvious that the package will be installed disabled by default.
* Secondly, every upgrade will suggest changing it back to disabled.
Revision history for this message
| marco.pallotta (marco-pallotta) wrote | #1 |
To post a comment you must log in.
I think the problem is not just that ENABLED is equal to 0 by default but that an entry ENABLED exists in /etc/default/
Why?
I haven't found any way that can demonstrate the fact that ENABLED should be useful. We already have runlevel scripts to control the fact that a service is ENABLED or not.