| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | systemd: Add Documentation references | Peter Rajnoha | 2012-06-20 | 1 | -0/+1 |
| | | | | | These documentation references show up in "systemctl status" output. | ||||
| * | Use SD_ACTIVATION env. var. in systemd units to better detect systemd in use. | Peter Rajnoha | 2012-03-14 | 1 | -0/+1 |
| | | | | | | | | | LISTEN_PID and LISTEN_FDS environment variables are defined only during systemd "start" action. But we still need to know whether we're activated during "reload" action as well - we use the reload action to call "dmeventd -R"/"lvmetad -R" for statefull daemon restart. We can't use normal "restart" as that is simply composed of "stop" and "start" and we would lose any state the daemon has. | ||||
| * | Clean up systemd unit ordering and requirements. | Peter Rajnoha | 2012-02-01 | 1 | -1/+2 |
| | | |||||
| * | Add "ExecReload" to dm-event.service for systemd to reload dmeventd properly. | Peter Rajnoha | 2011-10-31 | 1 | -0/+1 |
| | | | | | | | | | | | | | | Normally, restart simply means "stop and start" for systemd. However, if we're installing new versions of the dmeventd binary/libdevmapper, we need to restart dmeventd. This fails if we have some devices monitored - we need to call "dmeventd -R" instead. The "ExecReload" did not work quite well in some old versions of systemd, systemd assumed that only the configuration is reloaded on "ExecReload", not the whole binary itself so it lost track of dmeventd daemon (it lost new dmeventd PID). This is fixed and seems to be working fine now with recent versions of dmeventd. | ||||
| * | Add systemd unit files for dmeventd. | Peter Rajnoha | 2011-07-28 | 1 | -0/+14 |
 |
index : lvm2.git | |
| Andy Grover's LVM tree | Andy Grover |
| summaryrefslogtreecommitdiffstats |