Revision 4f060616
Added by Ermal LUÇI about 15 years ago
| etc/inc/gwlb.inc | ||
|---|---|---|
| 238 | 238 |
fwrite($fd, $apingerconfig); |
| 239 | 239 |
fclose($fd); |
| 240 | 240 |
|
| 241 |
if(!is_process_running("apinger")) {
|
|
| 241 |
if (is_process_running("apinger")) {
|
|
| 242 |
sigkillbypid("{$g['varrun_path']}/apinger.pid", "HUP");
|
|
| 243 |
} else {
|
|
| 242 | 244 |
if (is_dir("{$g['tmp_path']}"))
|
| 243 | 245 |
chmod("{$g['tmp_path']}", 01777);
|
| 244 | 246 |
if (is_dir("{$g['vardb_path']}/rrd"))
|
| ... | ... | |
| 246 | 248 |
/* start a new apinger process */ |
| 247 | 249 |
mwexec_bg("/usr/local/sbin/apinger -c {$g['varetc_path']}/apinger.conf");
|
| 248 | 250 |
} |
| 251 |
|
|
| 249 | 252 |
return 0; |
| 250 | 253 |
} |
| 251 | 254 |
|
Also available in: Unified diff
Actually send the HUP signal to tell apinger that a new config file is to be loaded! This should solve a lot of issues with apinger monitoring.