19b8f82 copr-be: we shouldn't use both cronolog and logrotate

Authored and Committed by praiskup 3 years ago
    copr-be: we shouldn't use both cronolog and logrotate
    
    These implications constraint us:
    
        max-workers is used => cronolog needs to be used
        log counter enabled => we need logrotate
    
    But:
        when logrotate is used => cronlog doesn't detect rotation
    
    So the '4c4b63516da9128342e8705244a91a09b1b9ff77' is IMO explained.
    Cronolog kept writing the log to the old descriptor, and the new
    access.log link was just empty (before 4c4b63516da912834 when we just
    reloaded, not restarted).  So I hope now that there isn't any other
    problem that would require us to restart Lighty regularly.
    
    The **UGLY** work-around is to terminate the cronlog process.  As I've
    found out, cronlog is automatically restarted by mod_accesslog - though
    this is somewhat gray zone and we should long-term do one of those:
    
        - stop using logrotate && rework log counter
        - stop using max-workers && cronlog
        - stop using Lighty
    
    Resolves: https://pagure.io/copr/copr/issue/2001
    Resolves: https://pagure.io/fedora-infrastructure/issue/10391