We're now in a systemd world where systemd is managing the restart
effectively, there is no reason to be tricksy with apache now that
we're not working around weird upstartd issues.
Change-Id: Ifadfd504eb10a90db5177ea9180b9cd8331a2948
| ... | ... |
@@ -173,11 +173,7 @@ function restart_apache_server {
|
| 173 | 173 |
# Apache can be slow to stop, doing an explicit stop, sleep, start helps |
| 174 | 174 |
# to mitigate issues where apache will claim a port it's listening on is |
| 175 | 175 |
# still in use and fail to start. |
| 176 |
- time_start "restart_apache_server" |
|
| 177 |
- stop_service $APACHE_NAME |
|
| 178 |
- sleep 3 |
|
| 179 |
- start_service $APACHE_NAME |
|
| 180 |
- time_stop "restart_apache_server" |
|
| 176 |
+ restart_service $APACHE_NAME |
|
| 181 | 177 |
} |
| 182 | 178 |
|
| 183 | 179 |
# reload_apache_server |