Apache HTTP Server Version 2.5

Apache > HTTP Server > Documentation > Version 2.5 > Modules

# Apache Module mod_systemd

Available Languages: en | fr

Description: | Provides better support for systemd integration
Status: | Extension
Module Identifier: | systemd_module
Source File: | mod_systemd.c

### Summary

This module provides support for systemd integration. It allows starting httpd as a service with systemd `Type=notify` (see systemd.service(5) manual page for more information). It also provides statistics in `systemctl status` output and adds various directives useful for systemd integration.

### Directives

### Bugfix checklist

- httpd changelog
- Known issues
- Report a bug

### See also

- Comments

## IdleShutdown Directive ¶

Description: | Enable shutting down the httpd when it is idle for some time.
Syntax: | `IdleShutdown seconds`
Default: | `IdleShutdown 0`
Context: | server config
Status: | Extension
Module: | mod_systemd

The `IdleShutdown` directive enables shutting down the httpd when it is idle for some time. The idleness is based on bytes served, so if there are no bytes sent for some time defined by this directive, httpd will shutdown. By default, IdleShutdown is set to 0 meaning this feature is disabled.

This feature is useful in a combination with systemd socket activation (see systemd.socket(5) manual page). When httpd is started by systemd on some request, using this directive you can stop the httpd automatically when all the requests are served.

### Implementation warning

Because of implementation details, idleness is checked only every 10 seconds. That means that if you specify `IdleShutdown 14`, httpd will stop itself after 20 seconds of idleness.

Available Languages: en | fr

## Comments

Notice:
This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.