• Thomas Gambier's avatar
    do not create two wrappers for the same executable if hash change · ed707d3b
    Thomas Gambier authored
    Prevent creating 2 wrapper for the same service if hash changed. Here, one service is exited because port is used by the firt to service to start:
        slappart6:runner-sshd-4248650e36a9a26a6481df1baffd9f58-on-watch                RUNNING   pid 27835, uptime 0:03:45
        slappart6:runner-sshd-b3b68f4278ceb84691ec27521ea229eb-on-watch                EXITED    Mar 06 04:52 PM
    To achieve that, update slapos.cookbook and use hash-existing-files option of wrapper recipe
    hash-existing-files list all the files used for hash that are not
    handled by buildout. For those files, the hash is calculated as soon as
    the __init__ function so that if there is a change in those files,
    buildout will remove the existing wrapper (it will uninstall the
    section) and replace it with the new wrapper.
    /reviewed-on nexedi/slapos!525
Last commit
Last update
buildout.cfg Loading commit data...
buildout.hash.cfg Loading commit data...
instance-logrotate-base.cfg.in Loading commit data...
logrotate.conf.in Loading commit data...
logrotate_entry.in Loading commit data...