Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • dev
  • resolve
  • parser
  • patch-1
  • async
  • boot
  • state
  • 0.8.0.2
  • 0.8.0.1
  • 0.8.0.0
  • 0.7.2.1
  • 0.7.2.0
  • 0.7.1.1
  • 0.7.1.0
  • 0.7.0.2
  • 0.7.0.1
  • 0.7.0.0
  • 0.7.0.0-preprod-rev2
  • 0.7.0.0-preprod-rev1
  • 0.7.0.0-preprod
  • 0.7.0.0-beta-3
  • 0.7.0.0-beta-2
  • 0.7.0.0-beta
  • v0.6.2.0
  • v0.6.1.3
  • v0.6.1.2
  • v0.6.1.1
28 results
Blame Permalink
  • Eric Vidal's avatar
    afd3dbe4
    Add the 66-execute program. · afd3dbe4
    Eric Vidal authored 
    This program is executed via the run script in the service's live directory. It sits between s6-supervise and the user's executable script, allowing for the preparation of the user's script execution. This introduces a dual capability:

    Define certain preparations through frontend keys, such as setting ownership, moving to a working directory, limiting resources used by the service, etc.
    Since 66-execute runs on each signal received and transmitted by s6-supervise, it is now possible to send messages to an event management daemon.

By default, this program performs previously defined actions such as logging redirections and managing environment variables (previously handled by excel-envfile), creation of the log destination directory, and so on.So, the user's file now contains only the exact copy of the @execute field.
Also, the name of the script for an start or
stop process are the same. This was a old behabvior
coming from s6-rc  manager.
    afd3dbe4
    History
    Add the 66-execute program.
    Eric Vidal authored 
    This program is executed via the run script in the service's live directory. It sits between s6-supervise and the user's executable script, allowing for the preparation of the user's script execution. This introduces a dual capability:

    Define certain preparations through frontend keys, such as setting ownership, moving to a working directory, limiting resources used by the service, etc.
    Since 66-execute runs on each signal received and transmitted by s6-supervise, it is now possible to send messages to an event management daemon.

By default, this program performs previously defined actions such as logging redirections and managing environment variables (previously handled by excel-envfile), creation of the log destination directory, and so on.So, the user's file now contains only the exact copy of the @execute field.
Also, the name of the script for an start or
stop process are the same. This was a old behabvior
coming from s6-rc  manager.
modes 425 B 
66                  0755
66-shutdown         0755
66-shutdownd        0755
66-hpr              0755
66-umountall        0755
66-echo             0755
66-execute          0755
66-nuke             0755
66-oneshot          0755
66-fdholder-filler  0755
execl-envfile       0755
init                0755
init.conf           0644
rc.init             0755
rc.init.container   0755
rc.shutdown         0755
rc.shutdown.final   0755