Rename TimeoutKill to TimeoutStart.
Rename TimeoutFinish to TimeoutStop.
Remove TimeoutUp and TimeoutDown key.
To avoid confusion and mistake, oneshot and classic service use now
the same key name to declare the timeout to use.
TimeoutStart and TimeoutStop are clearer than TimeoutKill and TimeoutFinish.
66 is sufficiently smart to name the file correctly for s6-supervise
whick look for the timeout-kill and timeout-finish file.

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.

use tmpfs directory as service directory for the runtime. Deal with logger destination directory at init time

Parse the service and write the result in a temporary directory. When the write process
is finished the directory is copied to the original service directory overwritten a
same file. The symlink /var/lib/66/system/.resolve/service/<name> is made at the complete
end of the process. So we can clean the mess removing the temporary directory and
avoid to change the original service directory before the end of the process. The state of
system should be clean event on crash of the parse process

Directories are handled by sanitize_write