Bug #2416
Version 1.4.30 - Minor config problem: config_read: Assertion `context.all_configs->used == 0' failed.
| Status: | Fixed | Start date: | 2012-04-28 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 100% | |
| Category: | - | |||
| Target version: | 1.4.31 | |||
| Missing in 1.5.x: | No |
Description
Hi,
I found out that giving -f more than once can cause problems.
lighttpd -f lighttpd.conf -f lighttpd.conf
It was the same .conf file btw (which was my accident, I just found out that lighttpd hates this)
Lighttpd then will say:
lighttpd: configfile.c:1101: config_read: Assertion `context.all_configs->used == 0' failed.
Aborted
And it will abort.
When I first had this problem, it was not obvious to me why it happened (I used an alias actually and then just appended -f again to this alias, which used -f already).
The error message: "Assertion failed" was not useful to me.
Proposal:
Make this specific error message more useful in case a user uses the -f option twice (or more than once).
Suggestion for error message, in case of abort-like problems:
"You seem to be using the -f option more than once."
"Please review your configuration files as they may contradict each other."
And then a listing which specific configuration option is in conflict perhaps - that would be most helpful.
Associated revisions
Detect multiple -f options: show error message instead of assert (fixes #2416)
History
#1 Updated by stbuehler about 1 year ago
- Target version changed from 1.4.x to 1.4.31
#2 Updated by stbuehler about 1 year ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset r2836.
Also available in: Atom