Watch for file changes and auto restart an application using fork checkpoints to continue. Intended for quick live development. This works only on Linux systems.
Small example of compiling
forkmon and using with Lua to reload scripts on the middle:
git clone https://github.com/edubart/forkmon.git && cd forkmon make alias forkmon-lua='LD_PRELOAD=`pwd`/forkmon.so FORKMON_FILTER="%.lua$" lua' forkmon-lua tests/example.lua
Now when running the above you should get something like:
[forkmon] watch '/home/bart/projects/forkmon/example.lua' startup [forkmon] watch '/home/bart/projects/forkmon/foo.lua' foo! finished
The application will keep running, waiting for any watched file change. Now try to edit to
foo.lua and change the print to
'hello world!', you should get something like:
[forkmon] file '/home/bart/projects/forkmon/tests/foo.lua' changed, resuming from it.. hello world! finished
Notice that only
'hello world!' is printed, but not
'startup', this means the application did not restart from beginning, but from the middle instead! Because a forked (cloned) application was waiting for changes in the
foo.lua and resumed.
How it works
fork() function has the interesting property of cloning a child process when called, the child process memory remains the same as the parent process, however both can run independently, each one with its own state and memory. But this is not a heavy operation, the process memory is not duplicated, instead copy on write is used, thus this is a lightweight operation. This property of
fork() allows to us to create checkpoints of the program that we can later use to resume a new process from the checkpoint without require the application to start from beginning, effectively rolling back state and memory in time. If we hook all
fopen() calls we can make checkpoints every time a file is opened, then using inotify Linux API we can watch files for changes and once a file change is detected we can resume a new process from its checkpoint instead of restarting the whole application. This allows to gain a few startup time in live development scenarios.
The tool can be configured using the following environment variables:
FORKMON_FILTERpattern that a watched file name should match, following Lua pattern rules, multiple filter patterns can be used when using the
FORKMON_QUIETif set, the tool will be quiet and not print anything.
FORKMON_NO_COLORSif set, no colors will be used in terminal output.
FORKMON_RESTART_DELAYhow many milliseconds to wait before restarting the application when a file has changed (default 20). Must be more than 0, so the OS can properly flush all file changes.
FORKMON_IGNORE_DELAYhow many milliseconds to ignore new changes after a file has been changed (default 200). Must be more than 0, so when saving files in a batch does not trigger many restarts.
I had this idea other day when thinking in ways to speedup the Nelua compiler, this tool can be used there to skip redundant compiler work. Because usually when you edit a source file the compiler needs to go parsing all sources again, even things before the source file change. This tool is a "hacky" way to allow the compiler to skip parsing and analyzing everything before a source file change. And if the sources are designed in such a way that a separate single source file requires all hardly ever changing files (similar to precompiled headers in C world), then the compilation can be much faster by skipping lots of parsing.
Although this was made for quick live development with Nelua on Linux, it can be used to speedup other console applications or compilers. And probably even servers that goes through a lot of loading and processing during startup, though the server startup need to be designed in such way that the checkpoints places does not have networking or multithreading going on.
- Only works well with application where all state to checkpoint is available in CPU memory, such as single threaded console applications. This is not the case for networking, graphical or multithreading applications, to make it work in such kind of applications extra work would be needed.
- The application must use
fopen64to open files, as these are the only file opening functions hooked. Some applications uses the
openatsyscall and this case will be missed.
- The application should not launch sub processes, thus this tool does not work well with GCC/Clang compilers as they launch itself when compiling, however it works with TCC compiler thus TCC could be even faster for live development!
- File descriptor offset are shared between processes (a
fork()behavior), and this can be problematic for applications that keep files open instead of caching them in memory.
In case you get the error
[forkmon] failed to initialize inotify then is probably because too many inotify instances are active, then try to increase this limit with
sudo sysctl -w user.max_inotify_instances=1024 or kill any zombie processes of the application (in edge cases can happen).
This has been implemented using the Nelua programming language, however a standalone C file is bundled in the repository, thus just a C compiler is needed to compile the project.
MIT License, see LICENSE