-
4.1385484178 · ·
Finit v4.13 GA - `initctl signal` command has been renamed to `initctl kill` - Drop xz tarballs from distribution, gzip is good enough - New `tmpfiles` stand-alone program, refactored from the existing tmpfiles.d support in Finit, by Aaron Andersen, PR #439 - `--remove` command runs only the `r` and `R` rules - `--create` is used for all other cases (bootstrap) - All `notify:systemd` services now log with `logit` by default. This because it supports systemd style log severity, leading `"<NUM>"` - Support for quoted arguments to run/task/service options, issue #441 - Clear command line arguments after bootstrap, issue #442 - Support for `stop:'script [args]'` to stop a sysv/service instead of the common `foo-stop-start.sh stop`, or `SIGTERM`, issue #412 - Support for `reload:'script [args]'` to trigger a configuration reload in a service, issue #446 - Fix #437: buffer overflow in `initctl status` - Fix #438: support very long command lines in `initctl ps/top` - Fix #440: broken systemd and s6 readiness notification - Fix #443: build warnings, by Ming Liu, Atlas Copco - Fix #444: handle loooooong arguments, by Aaron Andersen - Fix service's redirected stdout/stderr log priority in fallback mode, when neither `logger` or `logit` is available. This fix also checks for systemd style log severity, leading `"<NUM>"` in log messages - Ensure API socket used by `initctl` is non-blocking (event loop) Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
-
4.13-rc14f018563 · ·
Finit v4.13-rc1 - Drop xz tarballs from distribution, gzip is good enough - New `tmpfiles` stand-alone program, refactored from the existing tmpfiles.d support in Finit, by Aaron Andersen, PR #439 - `--remove` command runs only the `r` and `R` rules - `--create` is used for all other cases (bootstrap) - All `notify:systemd` services now log with `logit` by default. This because it supports systemd style log severity, leading `"<NUM>"` - Support for quoted arguments to run/task/service options, issue #441 - Clear command line arguments after bootstrap, issue #442 - Support for `stop:'script [args]'` to stop a sysv/service instead of the common `foo-stop-start.sh stop`, or `SIGTERM`, issue #412 - Support for `reload:'script [args]'` to trigger a configuration reload in a service, issue #446 - Fix #437: buffer overflow in `initctl status` - Fix #438: support very long command lines in `initctl ps/top` - Fix #440: broken systemd and s6 readiness notification - Fix #443: build warnings, by Ming Liu, Atlas Copco - Fix #444: handle loooooong arguments, by Aaron Andersen - Fix service's redirected stdout/stderr log priority in fallback mode, when neither `logger` or `logit` is available. This fix also checks for systemd style log severity, leading `"<NUM>"` in log messages - Ensure API socket used by `initctl` is non-blocking (event loop) Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
-
-
-
4.11185a72bd · ·
Finit v4.11 GA - Update documentation regarding transition from runlevel S to 2, how run/tasks must "complete" before Finit can move to the next runlevel - Improve argument handling in bundled getty when launching login - Fix #432: allow services in `setup` state to be stopped. This fixes a serious blocker introduced in 4.10 that prevented systems from being rebooted when any service was in this state - Fix fallback `SIGKILL` when stopping a service with `SIGTERM` does not work. This fixes a serious issue with services not responding to the default `SIGTERM` - Fix pre/post/ready/cleanup script execution if service has an optional `env:file` (leading `-`) - Fix blocked signals for pre/post/ready/cleanup scripts preventing normal shutdown when a service/sysv is stopped in its setup state - Fix issue where a pre:script creates a PID file in `/run` cause the service to move from setup state to running. Any `svc_t` in setup, teardown, or cleanup state should be ignored in the pidfile plugin Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
-
4.11-rc25e9591d0 · ·
Finit 4.11-rc2 - Update documentation regarding transition from runlevel S to 2, how run/tasks must "complete" before Finit can move to the next runlevel - Improve argument handling in bundled getty when launching login - Fix #432: allow services in `setup` state to be stopped. This fixes a serious blocker introduced in 4.10 that prevented systems from being rebooted when any service was in this state - Fix fallback `SIGKILL` when stopping a service with `SIGTERM` does not work. This fixes a serious issue with services not responding to the default `SIGTERM` - Fix pre/post/ready/cleanup script execution if service has an optional `env:file` (leading `-`) Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
-
4.11-rc1e3bcf9bf · ·
Finti 4.11-rc1 - Update documentation regarding transition from runlevel S to 2, how run/tasks must "complete" before Finit can move to the next runlevel - Improve argument handling in bundled getty when launching login - Fix #432: allow services in `setup` state to be stopped. This fixes a serious blocker introduced in 4.10 that prevented systems from being rebooted when any service was in this state - Fix fallback `SIGKILL` when stopping a service with `SIGTERM` does not work. This fixes a serious issue with services not responding to the default `SIGTERM` - Fix pre/post/ready/cleanup script execution if service has an optional `env:file` (leading `-`) Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
-
-
debian/4.7-39f8e130f · ·
-
debian/4.7-2a129d84b · ·
-
debian/4.7-190e4f00a · ·