Adam Warner add6973a28 Monitor the capsh pid, not FTL pid. If stop is called without an exit code being passed to it, then FTL is still running - so we stop FTL and then get the exit code from the capsh PID by immediately waiting it after killing FTL ...

Signed-off-by: Adam Warner <me@adamwarner.co.uk>

2024-10-09 21:56:57 +01:00

..

.dockerignore

Reorganise the repository

2022-07-15 17:43:09 +01:00

bash_functions.sh

Clean up the code - at the end of the start() function, wait for the start_ftl process and pass it's exit code to stop.

2024-10-07 21:54:55 +01:00

crontab.txt

Create our own cron file rather than copying the one from the core repo (which contains non-standard cron syntax)

2023-07-03 22:54:49 +01:00

Dockerfile

Actually do something with the result of readelf in case of invalid FTL binary

2024-09-11 19:09:35 +01:00

start.sh

Monitor the capsh pid, not FTL pid. If stop is called without an exit code being passed to it, then FTL is still running - so we stop FTL and then get the exit code from the capsh PID by immediately waiting it after killing FTL

2024-10-09 21:56:57 +01:00