On 03/03/2017 06:17 AM, Eliezer Croitoru wrote: > one of the options is to fence the ssl_crtd with some kind of lock > mechanism for the DB rebuild time. ssl_crtd already has a lock mechanism. If that mechanism is buggy, it needs to be fixed, but it does not make sense to add another one. There is still a lot of room for improvements, of course. For example, compared to a log-monitoring watchdog mentioned by Yuri: * Teaching ssl_crtd to run a sysadmin-provided script on database failures will allow the sysadmin to handle such failures almost transparently to the users and may reduce configuration headaches associated with ssl_crtd message text changes. * Teaching Squid to run a sysadmin-provided script on helper crashes will allow the sysadmin to handle such failures more transparently to the users and may reduce configuration headaches associated with helper message text changes. Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
