It appears that the subject fix has the following nasty effect, at least with Python 3.4
> Jan 29 00:00:13 2017 (7099) Master watcher caught SIGHUP. Re-opening log > files. > Jan 29 00:00:13 2017 (8568) in runner caught SIGHUP. Reopening logs. > Jan 29 00:00:13 2017 (8566) pipeline runner caught SIGHUP. Reopening logs. > Jan 29 00:00:13 2017 (8568) in runner exiting. > Jan 29 00:00:13 2017 (8566) pipeline runner exiting. > Jan 29 00:00:13 2017 (8569) retry runner caught SIGHUP. Reopening logs. > Jan 29 00:00:13 2017 (8569) retry runner exiting. ... I.e. when logrotate SIGHUPs the master to reopen logs, all the runners except for 'rest' exit. Ordinarily, I'd report this on GitLab, but they are having problems of their own right now. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
