Project

General

Profile

Actions
Copy link

Feature #867

closed

Config file runtime reloading

Added by icy over 17 years ago. Updated 2 months ago.

Status:
Fixed
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:
No

Description

It would be very usefull to be able to reload the config file at runtime (maybe per signal?) without restarting lighttpd.
The graceful restart is no perfect solution.

Actions
Copy link
 #1

Updated by mike503 almost 17 years ago

agreed.

or have some conf.d style thing that is monitored/checked every so often.

having to reload the entire server for a one line rewrite rule added seems obnoxious... i was just thinking of filing a RFE for this myself!

Actions
Copy link
 #2

Updated by ts77 over 16 years ago

Would be very interested in a solution to this too.
(Like many others, just see that thread http://forum.lighttpd.net/topic/1195 )

Actions
Copy link
 #3

Updated by stbuehler over 15 years ago

  • Status changed from New to Fixed
  • Resolution set to wontfix

That wouldn't solve the problem, so just use the graceful restart. If you care about your fastcgi processes: it would be really hard work to keep them (and probably very buggy); just spawn them with "spawn-fcgi".

Actions
Copy link
 #4

Updated by stbuehler over 15 years ago

  • Status changed from Fixed to Wontfix
Actions
Copy link
 #5

Updated by gstrauss 2 months ago

  • Description updated (diff)
  • Status changed from Wontfix to Fixed
  • ASK QUESTIONS IN Forums set to No

Since lighttpd 1.4.56, for a subset of configurations where it is safe to do so, lighttpd can be configured to perform an immediate restart while still serving existing connections.

server.feature-flags

server.feature-flags += ("server.graceful-restart-bg" => "enable")
immediate graceful restart while existing requests complete in background process (default: disable)
Note: feature works with many lighttpd.conf configurations, but not available in all configurations
(e.g. available with independent backends; not available if lighttpd runs backend processes with "bin-path"

Note that continuing to serve existing connections has a configurable timeout before those existing connections are shut down.
The default is 8 seconds (since lighttpd 1.4.64)
server.feature-flags += ("server.graceful-shutdown-timeout" => 8)

Actions
Copy link

Also available in: Atom