*CHECKPOINTCTL-PLUGIN*(1)
π CHECKPOINTCTL-PLUGIN π
okay bestie, welcome to the checkpointctl-plugin page from the CHECKPOINTCTL manual β¨ this is literally the guide to managing checkpointctl plugins and it's lowkey adorable how simple it is π
πΈ NAME πΈ
checkpointctl-plugin β manage checkpointctl plugins π
β¨ SYNOPSIS β¨
checkpointctl plugin COMMAND
π¦ DESCRIPTION π¦
so the checkpointctl plugin command is the one that manages external plugins β little add-ons that extend checkpointctl with extra subcommands π«Ά
Plugins are standalone executables that live in PATH, and their names have to match the pattern checkpointctl-<name>. When checkpointctl starts up, it goes and discovers these plugins and registers them as subcommands, no cap π So like, if checkpointctl-foo exists in PATH, boom, it becomes available as checkpointctl foo.
The whole point of this plugin architecture? Extending checkpointctl's functionality without making the core tool's binary size grow π And the best part β plugins can be implemented in any programming language. literally any. go feral π§
π COMMANDS π
listβ List all available plugins discovered inPATH. β¨
π PLUGIN DEVELOPMENT π
To create a plugin, here's the lil ritual π
- Create an executable named
checkpointctl-<name>(e.g.,checkpointctl-hello) - Place it in a directory included in
PATH - Make it executable (
chmod +x)
πΈ Plugin Description πΈ
Plugins can provide a description that shows up in checkpointctl --help by supporting the --plugin-description flag π«Ά And here's the lil secret: the plugin must exit with code 42 to indicate that it supports this flag:
#!/bin/sh
if [ "$1" = "--plugin-description" ]; then
echo "My plugin description"
exit 42
fi
# Normal plugin logic here
bestie listen β if a plugin does not exit with code 42 when it gets called with --plugin-description, then a default description showing the plugin path gets used instead. so 42 is the magic number, iykyk π«
π OPTIONS π
-h,--helpβ Show help forcheckpointctl pluginπ
π₯ EXAMPLES π₯
List available plugins:
$ checkpointctl plugin list
Run a plugin (assuming checkpointctl-hello exists in PATH):
$ checkpointctl hello
π SEE ALSO π
π AUTHOR π
The CRIU team π
and that's the whole page bestie, slay β¨ this was checkpointctl, dated 2026-10-19, from the CHECKPOINTCTL manual β go forth and plugin, you absolute icon ππ¦π
π¦ where this page comes from
- fedora 43: checkpointctl 1:1.7.0-2.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND MIT AND MPL-2.0
- fedora 44: checkpointctl 1:1.7.0-2.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND MIT AND MPL-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms