systemd-ts 261.3.0 → 262.1.0

package/README.md

@@ -12,26 +12,18 @@ It is designed around a few practical jobs:
 
 The library has two layers:
 
-- `systemd.ts.*` is the code-owned upkeep layer for attaching, reattaching, and
-  detaching application-managed units.
-- `systemd.*` stays close to raw `systemd` concepts like materializing units and
-  starting them directly.
+- `systemd.ts.*` is the code-owned upkeep layer for attaching, reattaching, and detaching application-managed units.
+- `systemd.*` stays close to raw `systemd` concepts like materializing units and starting them directly.
 
-That lets the README start from the application code story without giving up a
-lower-level `systemd` surface when you want it.
+That lets the README start from the application code story without giving up a lower-level `systemd` surface when you want it.
 
-It is also a good place to learn `systemd` itself. The unit directives are
-deeply typed, documented in the TypeScript surface, and maintained against
-versioned upstream manpage material, so the library doubles as a guided way to
-explore what `systemd` can do without starting from loose strings and scattered
-shell examples.
+It is also a good place to learn `systemd` itself. The unit directives are deeply typed, documented in the TypeScript surface, and maintained against versioned upstream manpage material, so the library doubles as a guided way to explore what `systemd` can do without starting from loose strings and scattered shell examples.
 
 ## What It Can Do
 
 ### Keep application-owned units up to date
 
-If your application owns a service or timer and wants to keep that unit set up
-to date across reinstalls, updates, or reconfiguration, use `systemd.ts`.
+If your application owns a service or timer and wants to keep that unit set up to date across reinstalls, updates, or reconfiguration, use `systemd.ts`.
 
 ```ts
 import { homedir } from "node:os";
@@ -77,10 +69,7 @@ if (!attached.ok) {
 }
 ```
 
-This is the highest-level upkeep workflow in the library. It is designed for
-desktop apps, self-updating agents, OTA-managed software, and other code-owned
-service setups where the application itself is responsible for the unit set it
-maintains.
+This is the highest-level upkeep workflow in the library. It is designed for desktop apps, self-updating agents, OTA-managed software, and other code-owned service setups where the application itself is responsible for the unit set it maintains.
 
 ### Use `systemctl` from TypeScript
 
@@ -105,9 +94,7 @@ console.log(timers.value);
 console.log(status.value);
 ```
 
-This is a good fit when you already know the units you want to inspect or
-control and you want to stay inside TypeScript instead of shelling out from app
-code by hand.
+This is a good fit when you already know the units you want to inspect or control and you want to stay inside TypeScript instead of shelling out from app code by hand.
 
 ### Define a service from TypeScript
 
@@ -130,8 +117,7 @@ const service = new SystemdService({
 });
 ```
 
-That service can be rendered into a real unit file, materialized into a unit
-directory, and then managed through `Systemd` or `Systemctl`.
+That service can be rendered into a real unit file, materialized into a unit directory, and then managed through `Systemd` or `Systemctl`.
 
 ### Define a service that runs on a timer
 
@@ -164,13 +150,11 @@ const timer = new SystemdTimer({
 });
 ```
 
-This gives you a real `.service` plus a real `.timer`, both defined from the
-same TypeScript module.
+This gives you a real `.service` plus a real `.timer`, both defined from the same TypeScript module.
 
 ### Keep the executable close to the unit definitions
 
-For many projects, the nicest workflow is to colocate the job entrypoint with
-the service and timer that run it.
+For many projects, the nicest workflow is to colocate the job entrypoint with the service and timer that run it.
 
 `defineExecutable()` is designed for that pattern:
 
@@ -208,8 +192,7 @@ const timer = new SystemdTimer({
 });
 ```
 
-That keeps the scheduled code, the service definition, and the timer definition
-near each other instead of scattering them across shell scripts and unit files.
+That keeps the scheduled code, the service definition, and the timer definition near each other instead of scattering them across shell scripts and unit files.
 
 ## A Typical Flow
 
@@ -266,8 +249,7 @@ if (!reattached.ok) {
 
 ### Using The `Systemd` API Directly
 
-If you want to stay closer to raw `systemd` operations, use the lower-level
-`Systemd` methods directly:
+If you want to stay closer to raw `systemd` operations, use the lower-level `Systemd` methods directly:
 
 ```ts
 import { homedir } from "node:os";
@@ -318,18 +300,13 @@ if (!started.ok) {
 }
 ```
 
-This lower-level flow is useful when you want exact control over
-materialization, enablement, or startup behavior without going through the
-code-owned upkeep layer.
+This lower-level flow is useful when you want exact control over materialization, enablement, or startup behavior without going through the code-owned upkeep layer.
 
 ## Testing Against A Real User Manager
 
-The package also ships a `systemd-ts/test` module for integration tests that
-need a real `systemd --user` environment.
+The package also ships a `systemd-ts/test` module for integration tests that need a real `systemd --user` environment.
 
-Use `ensureTestHost()` to warm the test host, `createTestSandbox()` to create
-an isolated unit directory, and `sandboxSystemd()` when you want a `Systemd`
-instance already pointed at that sandbox.
+Use `ensureTestHost()` to warm the test host, `createTestSandbox()` to create an isolated unit directory, and `sandboxSystemd()` when you want a `Systemd` instance already pointed at that sandbox.
 
 ```ts
 import { afterEach, beforeAll, beforeEach, test } from "vitest";
@@ -379,16 +356,13 @@ test(`starts a service in a sandbox`, async () => {
 });
 ```
 
-If you need direct executor access for helpers outside `Systemd`, the same
-module also exports `guestCommandExecutor`, `isolatedGuestCommandExecutor`, and
-`createGuestCommandExecutor()`.
+If you need direct executor access for helpers outside `Systemd`, the same module also exports `guestCommandExecutor`, `isolatedGuestCommandExecutor`, and `createGuestCommandExecutor()`.
 
 ## Explore Further
 
 The README is meant to answer what the library is for.
 
-If you want the exact method surface, result types, or lower-level details, the
-next places to look are:
+If you want the exact method surface, result types, or lower-level details, the next places to look are:
 
 - `Systemctl` for direct `systemctl` usage from TypeScript
 - `Systemd` for materialization plus unit lifecycle workflows

package/dist/{index-6lsBWH4h.d.mts → index-C9XrvZh3.d.mts}

@@ -203,6 +203,7 @@ type PressureWatchDirectiveValue = boolean | "auto" | "skip";
 type StandardInputDirectiveValue = "null" | "tty" | "tty-force" | "tty-fail" | "data" | "socket" | "fd" | `file:${string}` | `fd:${string}`;
 type StandardOutputDirectiveValue = "inherit" | "null" | "tty" | "journal" | "kmsg" | "journal+console" | "kmsg+console" | "socket" | "fd" | `file:${string}` | `append:${string}` | `truncate:${string}` | `fd:${string}`;
 type StandardErrorDirectiveValue = StandardOutputDirectiveValue | "inherit";
+/** Command lines for `Exec*=` directives. A `+` executable prefix bypasses per-command privilege restrictions and `Limit*=` settings, including manager-configured defaults; the command inherits the service manager's resource limits. Controls applying to the whole cgroup still apply. Source: systemd v262.1, `systemd.service(5)`. */
 type ExecDirective = string | Executable | readonly (string | Executable)[];
 type UnitValue = string | number | boolean | Executable;
 type UnitValueList = readonly UnitValue[];
@@ -213,10 +214,11 @@ interface CustomDirectiveSection {
 /**
  * Generic unit-level directives shared by service and timer units.
  *
- * References in this file are grounded in cached upstream systemd v260.1 manpages.
+ * References in this file are grounded in cached upstream systemd manpages,
+ * reviewed through v262.1. Individual directives identify their documentation source.
  *
  * Sources:
- * - systemd v260.1, `systemd.unit(5)`
+ * - systemd v262, `systemd.unit(5)`
  */
 interface SystemdUnitSection extends CustomDirectiveSection {
   /** Units that should be ordered before this unit starts. Source: systemd v260.1, `systemd.unit(5)`. */
@@ -227,7 +229,7 @@ interface SystemdUnitSection extends CustomDirectiveSection {
   readonly AssertACPower?: boolean | readonly boolean[];
   /** Assertion form of `ConditionArchitecture=`. Check whether the system is running on a specific architecture. Takes one of x86, x86-64, ppc, ppc-le, ppc64, ppc64-le, ia64, parisc, parisc64, s390, s390x, sparc, sparc64, mips, mips-le, mips64, mips64-le, alpha, arm, arm-be, arm64, arm64-be, sh, sh64, m68k, tilegx, cris, arc, arc-be, or native. Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly AssertArchitecture?: string | readonly string[];
-  /** Assertion form of `ConditionCPUFeature=`. Verify that a given CPU feature is available via the CPUID instruction. This condition only does something on i386 and x86-64 processors. On other processors it is assumed that the CPU does not support the given feature. It checks the leaves 1, 7, 0x80000001, and 0x80000007. Valid values are: fpu, vme, de, pse, tsc, msr, pae, mce, cx8, apic, sep, mtrr, pge, mca, cmov, pat, pse36, clflush, mmx, fxsr, sse, sse2, ht, pni, pclmul, monitor, ssse3, fma3, cx16, sse4_1, sse4_2, movbe, popcnt, aes, xsave, osxsave, avx, f16c, rdrand, bmi1, avx2, bmi2, rdseed, adx, sha_ni, syscall, rdtscp, lm, lahf_lm, abm, constant_tsc. Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v260.1, `systemd.unit(5)`. */
+  /** Assertion form of `ConditionCPUFeature=`. Checks CPU features via CPUID on i386 and x86-64, or ELF hardware capabilities on arm64. Accepts architecture-qualified names such as `arm64.bti`; a mismatched architecture prefix evaluates to false. On other architectures, features are assumed unsupported. Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v262, `systemd.unit(5)`. */
   readonly AssertCPUFeature?: string | readonly string[];
   /** Assertion form of `ConditionCPUPressure=`. Verify that the overall system (memory, CPU or IO) pressure is below or equal to a threshold. This setting takes a threshold value as argument. It can be specified as a simple percentage value, suffixed with %, in which case the pressure will be measured as an average over the last five minutes before the attempt to start the unit is performed. Alternatively, the average timespan can also be specified using / as a separator, for example: 10%/1min. The supported timespans match what the kernel provides, and are limited to 10sec, 1min and 5min. The full PSI will be checked first, and if not found some will be checked. For more details, see the documentation on PSI (Pressure Stall Information) . Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly AssertCPUPressure?: string | readonly string[];
@@ -263,7 +265,7 @@ interface SystemdUnitSection extends CustomDirectiveSection {
   readonly AssertKernelModuleLoaded?: string | readonly string[];
   /** Assertion form of `ConditionKernelVersion=`. May be used to check whether the kernel version (as reported by uname -r) matches a certain expression, or if prefixed with the exclamation mark, does not match. The argument must be a list of (potentially quoted) expressions. Each expression starts with one of = or != for string comparisons, <, <=, ==, <>, >=, > for version comparisons, or $=, !$= for a shell-style glob match. If no operator is specified, $= is implied. Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly AssertKernelVersion?: string | readonly string[];
-  /** Assertion form of `ConditionMachineTag=`. Matches machine tags configured in `machine-info(5)`. Source: systemd v261, `systemd.unit(5)`. */
+  /** Assertion form of `ConditionMachineTag=`. Matches machine tags using shell-style patterns, optionally negated with `!`. Parameterized tags include their value in the match: `role=web` matches exactly, `role=*` matches any value for that key, and `role` does not match `role=web`. Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v262, `systemd.unit(5)`. */
   readonly AssertMachineTag?: string | readonly string[];
   /** Assertion form of `ConditionMemory=`. Verify that the specified amount of system memory is available to the current system. Takes a memory size in bytes as argument, optionally prefixed with a comparison operator <, <=, = (or ==), != (or <>), >=, >. On bare-metal systems compares the amount of physical memory in the system with the specified size, adhering to the specified comparison operator. In containers compares the amount of memory assigned to the container instead. Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly AssertMemory?: number | string | readonly (number | string)[];
@@ -273,7 +275,7 @@ interface SystemdUnitSection extends CustomDirectiveSection {
   readonly AssertNeedsUpdate?: string | readonly string[];
   /** Assertion form of `ConditionOSRelease=`. Verify that a specific key=value pair is set in the host's os-release5. Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly AssertOSRelease?: string | readonly string[];
-  /** Assertion form of `ConditionPathExists=`. Check for the existence of a file. If the specified absolute path name does not exist, the condition will fail. If the absolute path name passed to ConditionPathExists= is prefixed with an exclamation mark (!), the test is negated, and the unit is only started if the path does not exist. Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v260.1, `systemd.unit(5)`. */
+  /** Assertion form of `ConditionPathExists=`. Checks for any file system object at an absolute path, including directories, device nodes, FIFOs, and sockets. Symbolic links are followed, so broken symbolic links do not count as existing. Prefix the path with `!` to require its absence. Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v262, `systemd.unit(5)`. */
   readonly AssertPathExists?: string | readonly string[];
   /** Assertion form of `ConditionPathExistsGlob=`. Similar to `ConditionPathExists=`, but checks for the existence of at least one file or directory matching the specified globbing pattern. Unlike conditions, a mismatch fails the start job instead of skipping it. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly AssertPathExistsGlob?: string | readonly string[];
@@ -307,7 +309,7 @@ interface SystemdUnitSection extends CustomDirectiveSection {
   readonly ConditionACPower?: boolean | readonly boolean[];
   /** Check whether the system is running on a specific architecture. Takes one of x86, x86-64, ppc, ppc-le, ppc64, ppc64-le, ia64, parisc, parisc64, s390, s390x, sparc, sparc64, mips, mips-le, mips64, mips64-le, alpha, arm, arm-be, arm64, arm64-be, sh, sh64, m68k, tilegx, cris, arc, arc-be, or native. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly ConditionArchitecture?: string | readonly string[];
-  /** Verify that a given CPU feature is available via the CPUID instruction. This condition only does something on i386 and x86-64 processors. On other processors it is assumed that the CPU does not support the given feature. It checks the leaves 1, 7, 0x80000001, and 0x80000007. Valid values are: fpu, vme, de, pse, tsc, msr, pae, mce, cx8, apic, sep, mtrr, pge, mca, cmov, pat, pse36, clflush, mmx, fxsr, sse, sse2, ht, pni, pclmul, monitor, ssse3, fma3, cx16, sse4_1, sse4_2, movbe, popcnt, aes, xsave, osxsave, avx, f16c, rdrand, bmi1, avx2, bmi2, rdseed, adx, sha_ni, syscall, rdtscp, lm, lahf_lm, abm, constant_tsc. Source: systemd v260.1, `systemd.unit(5)`. */
+  /** Checks CPU features via CPUID on i386 and x86-64, or ELF hardware capabilities on arm64. Accepts architecture-qualified names such as `arm64.bti`; a mismatched architecture prefix evaluates to false. On other architectures, features are assumed unsupported. Source: systemd v262, `systemd.unit(5)`. */
   readonly ConditionCPUFeature?: string | readonly string[];
   /** Verify that the overall system (memory, CPU or IO) pressure is below or equal to a threshold. This setting takes a threshold value as argument. It can be specified as a simple percentage value, suffixed with %, in which case the pressure will be measured as an average over the last five minutes before the attempt to start the unit is performed. Alternatively, the average timespan can also be specified using / as a separator, for example: 10%/1min. The supported timespans match what the kernel provides, and are limited to 10sec, 1min and 5min. The full PSI will be checked first, and if not found some will be checked. For more details, see the documentation on PSI (Pressure Stall Information) . Source: systemd v260.1, `systemd.unit(5)`. */
   readonly ConditionCPUPressure?: string | readonly string[];
@@ -345,7 +347,7 @@ interface SystemdUnitSection extends CustomDirectiveSection {
   readonly ConditionKernelModuleLoaded?: string | readonly string[];
   /** May be used to check whether the kernel version (as reported by uname -r) matches a certain expression, or if prefixed with the exclamation mark, does not match. The argument must be a list of (potentially quoted) expressions. Each expression starts with one of = or != for string comparisons, <, <=, ==, <>, >=, > for version comparisons, or $=, !$= for a shell-style glob match. If no operator is specified, $= is implied. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly ConditionKernelVersion?: string | readonly string[];
-  /** Matches machine tags configured in `machine-info(5)`. Source: systemd v261, `systemd.unit(5)`. */
+  /** Matches machine tags from `machine-info(5)` using shell-style patterns, optionally negated with `!`. Parameterized tags include their value in the match: `role=web` matches exactly, `role=*` matches any value for that key, and `role` does not match `role=web`. Source: systemd v262, `systemd.unit(5)`. */
   readonly ConditionMachineTag?: string | readonly string[];
   /** Verify that the specified amount of system memory is available to the current system. Takes a memory size in bytes as argument, optionally prefixed with a comparison operator <, <=, = (or ==), != (or <>), >=, >. On bare-metal systems compares the amount of physical memory in the system with the specified size, adhering to the specified comparison operator. In containers compares the amount of memory assigned to the container instead. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly ConditionMemory?: number | string | readonly (number | string)[];
@@ -355,7 +357,7 @@ interface SystemdUnitSection extends CustomDirectiveSection {
   readonly ConditionNeedsUpdate?: string | readonly string[];
   /** Verify that a specific key=value pair is set in the host's os-release5. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly ConditionOSRelease?: string | readonly string[];
-  /** Check for the existence of a file. If the specified absolute path name does not exist, the condition will fail. If the absolute path name passed to ConditionPathExists= is prefixed with an exclamation mark (!), the test is negated, and the unit is only started if the path does not exist. Source: systemd v260.1, `systemd.unit(5)`. */
+  /** Checks for any file system object at an absolute path, including directories, device nodes, FIFOs, and sockets. Symbolic links are followed, so broken symbolic links do not count as existing. Prefix the path with `!` to require its absence. Source: systemd v262, `systemd.unit(5)`. */
   readonly ConditionPathExists?: string | readonly string[];
   /** Similar to `ConditionPathExists=`, but checks for the existence of at least one file or directory matching the specified globbing pattern. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly ConditionPathExistsGlob?: string | readonly string[];
@@ -437,7 +439,7 @@ interface SystemdUnitSection extends CustomDirectiveSection {
   readonly StartLimitAction?: UnitActionDirectiveValue;
   /** See systemd.unit(5) for StartLimitBurst=. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly StartLimitBurst?: number;
-  /** Configure unit start rate limiting. Units which are started more than burst times within an interval time span are not permitted to start any more. Use StartLimitIntervalSec= to configure the checking interval and StartLimitBurst= to configure how many starts per interval are allowed. Source: systemd v260.1, `systemd.unit(5)`. */
+  /** Configure unit start rate limiting. Units which are started more than burst times within an interval time span are not permitted to start any more. Use StartLimitIntervalSec= to configure the checking interval and StartLimitBurst= to configure how many starts per interval are allowed. Since systemd v262, time spent suspended counts toward the interval. Sources: systemd v262, `systemd.unit(5)` and `NEWS`. */
   readonly StartLimitIntervalSec?: number | string;
   /** Units whose stop requests should also stop this unit. Source: systemd v260.1, `systemd.unit(5)`. */
   readonly StopPropagatedFrom?: string | readonly string[];
@@ -524,7 +526,7 @@ interface SystemdTimerSection extends CustomDirectiveSection {
  *
  * This interface includes directives from `systemd.service(5)`,
  * `systemd.exec(5)`, `systemd.kill(5)`, and
- * `systemd.resource-control(5)` as of systemd v260.1.
+ * `systemd.resource-control(5)`, reviewed through systemd v262.1.
  */
 interface SystemdServiceSection extends CustomDirectiveSection {
   /** This setting controls the cpuset controller in the unified hierarchy. Source: systemd v260.1, `systemd.resource-control(5)`. */
@@ -697,37 +699,37 @@ interface SystemdServiceSection extends CustomDirectiveSection {
   readonly KillMode?: "control-group" | "mixed" | "process" | "none";
   /** Specifies which signal to use when stopping a service. This controls the signal that is sent as first step of shutting down a unit (see above), and is usually followed by SIGKILL (see above and below). For a list of valid signals, see signal(7). Defaults to SIGTERM. Source: systemd v260.1, `systemd.kill(5)`. */
   readonly KillSignal?: NodeJS.Signals | number;
-  /** Maximum address-space size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum address-space size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitAS?: ProcessResourceLimitDirectiveValue;
-  /** Maximum core-file size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum core-file size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitCORE?: ProcessResourceLimitDirectiveValue;
-  /** Maximum CPU time for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum CPU time for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitCPU?: ProcessResourceLimitDirectiveValue;
-  /** Maximum data-segment size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum data-segment size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitDATA?: ProcessResourceLimitDirectiveValue;
-  /** Maximum created-file size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum created-file size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitFSIZE?: ProcessResourceLimitDirectiveValue;
-  /** Maximum number of file locks for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum number of file locks for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitLOCKS?: ProcessResourceLimitDirectiveValue;
-  /** Maximum locked-in-memory size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum locked-in-memory size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitMEMLOCK?: ProcessResourceLimitDirectiveValue;
-  /** Maximum POSIX message-queue size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum POSIX message-queue size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitMSGQUEUE?: ProcessResourceLimitDirectiveValue;
-  /** Maximum nice-priority adjustment for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum nice-priority adjustment for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitNICE?: ProcessResourceLimitDirectiveValue;
-  /** Maximum number of open file descriptors for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum number of open file descriptors for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitNOFILE?: ProcessResourceLimitDirectiveValue;
-  /** Maximum number of processes or threads for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum number of processes or threads for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitNPROC?: ProcessResourceLimitDirectiveValue;
-  /** Maximum resident-set size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum resident-set size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitRSS?: ProcessResourceLimitDirectiveValue;
-  /** Maximum real-time scheduling priority for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum real-time scheduling priority for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitRTPRIO?: ProcessResourceLimitDirectiveValue;
-  /** Maximum real-time CPU time for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum real-time CPU time for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitRTTIME?: ProcessResourceLimitDirectiveValue;
-  /** Maximum number of queued signals for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum number of queued signals for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitSIGPENDING?: ProcessResourceLimitDirectiveValue;
-  /** Maximum stack size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Maximum stack size for processes started by the unit. Accepts the usual `soft:hard` syntax, `infinity`, and unit suffixes where systemd allows them. Commands prefixed with `+` bypass this setting and its configured default, inheriting the service manager's resource limits instead. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly LimitSTACK?: ProcessResourceLimitDirectiveValue;
   /** Pass a credential to the unit. Credentials are limited-size binary or textual objects that may be passed to unit processes. They are primarily intended for passing cryptographic keys (both public and private) or certificates, user account information or identity information from host to services, but can be freely used to pass any kind of limited-size information to a service. The data is accessible from the unit's processes via the file system, at a read-only location that (if possible and permitted) is backed by non-swappable memory. The data is only accessible to the user associated with the unit, via the User=/DynamicUser= settings (as well as the superuser). When available, the location of credentials is exported as the $CREDENTIALS_DIRECTORY environment variable to the unit's processes. Source: systemd v260.1, `systemd.exec(5)`. */
   readonly LoadCredential?: string | readonly string[];
@@ -755,6 +757,8 @@ interface SystemdServiceSection extends CustomDirectiveSection {
   readonly LogsDirectoryMode?: string;
   /** Storage quota for directories created by `LogsDirectory=`. Source: systemd v260.1, `systemd.exec(5)`. */
   readonly LogsDirectoryQuota?: number | string;
+  /** Creates named Live Update Orchestrator (LUO) sessions and passes their file descriptors through the service's file descriptor store. Takes whitespace-separated names; repeated assignments are combined, and an empty string resets the list. Implies `FileDescriptorStoreMax=` is at least the number of sessions. Use `FileDescriptorStorePreserve=true` to preserve them across kexec. Existing sessions with the same name are reused. If `/dev/liveupdate` is unavailable, the service starts normally without sessions. Only supported by the system service manager. Source: systemd v262, `systemd.service(5)`. */
+  readonly LUOSession?: string | readonly string[];
   /** See systemd.service(5) for ManagedOOMMemoryPressure=. Source: systemd v260.1, `systemd.service(5)`. */
   readonly ManagedOOMMemoryPressure?: ManagedOOMDirectiveValue;
   /** Overrides the default memory pressure duration set by oomd.conf5 for the cgroup of this unit. The specified value supports a time unit such as ms or μs, see systemd.time(7) for details on the permitted syntax. Must be set to either empty or a value of at least 1s. Defaults to empty, which means to use the default set by oomd.conf5. This property is ignored unless ManagedOOMMemoryPressure=kill. Source: systemd v260.1, `systemd.resource-control(5)`. */
@@ -803,7 +807,7 @@ interface SystemdServiceSection extends CustomDirectiveSection {
   readonly NFTSet?: string | readonly string[];
   /** Controls the NUMA node list which will be applied alongside with selected NUMA policy. Takes a list of NUMA nodes and has the same syntax as a list of CPUs for CPUAffinity= option or special "all" value which will include all available NUMA nodes in the mask. Note that the list of NUMA nodes is not required for default and local policies and for preferred policy we expect a single NUMA node. Source: systemd v260.1, `systemd.exec(5)`. */
   readonly NUMAMask?: string | readonly string[];
-  /** Controls the NUMA memory policy of the executed processes. Takes a policy type, one of: default, preferred, bind, interleave and local. A list of NUMA nodes that should be associated with the policy must be specified in NUMAMask=. For more details on each policy please see, set_mempolicy(2). For overall overview of NUMA support in Linux see, numa(7). Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Controls the NUMA memory policy: `default`, `preferred`, `bind`, `interleave`, `local`, `preferred-many` (Linux 5.15 or newer), or `weighted-interleave` (Linux 6.9 or newer). Configure associated nodes with `NUMAMask=` and weighted-interleave weights through `/sys/kernel/mm/mempolicy/weighted_interleave/`. Unsupported kernel policies log a warning and are ignored. Source: systemd v262, `systemd.exec(5)`. */
   readonly NUMAPolicy?: string | readonly string[];
   /** Takes an absolute file system path referring to a Linux network namespace pseudo-file (i.e. a file like /proc/$PID/ns/net or a bind mount or symlink to one). When set the invoked processes are added to the network namespace referenced by that path. The path has to point to a valid namespace file at the moment the processes are forked off. If this option is used PrivateNetwork= has no effect. If this option is used together with JoinsNamespaceOf= then it only has an effect if this unit is started before any of the listed units that have PrivateNetwork= or NetworkNamespacePath= configured, as otherwise the network namespace of those units is reused. Source: systemd v260.1, `systemd.exec(5)`. */
   readonly NetworkNamespacePath?: string;
@@ -875,7 +879,7 @@ interface SystemdServiceSection extends CustomDirectiveSection {
   readonly ReadWritePaths?: string | readonly string[];
   /** Supports either booleans or a space-separated list of refreshable resource kinds such as `extensions` and `credentials`. Source: systemd v260.1, `systemd.service(5)`. */
   readonly RefreshOnReload?: boolean | string;
-  /** Configures the UNIX process signal to send to the service's main process when asked to reload the service's configuration. Defaults to SIGHUP. This option has no effect unless Type=notify-reload is used, see above. Source: systemd v260.1, `systemd.service(5)`. */
+  /** Selects the signal sent to the main process to reload a `Type=notify-reload` service. Defaults to SIGHUP and has no effect for other service types. The main process must catch or block this signal before its initial `READY=1` notification, or startup fails. The handler is checked again before reloading; a missing handler then causes a warning, but the signal is still sent. Source: systemd v262, `systemd.service(5)`. */
   readonly ReloadSignal?: NodeJS.Signals | number;
   /** Takes a boolean value that specifies whether the service shall be considered active even when all its processes exited. Defaults to no. Source: systemd v260.1, `systemd.service(5)`. */
   readonly RemainAfterExit?: boolean;
@@ -893,6 +897,8 @@ interface SystemdServiceSection extends CustomDirectiveSection {
   readonly RestartMode?: ServiceRestartModeDirectiveValue;
   /** Takes a list of exit status definitions that, when returned by the main service process, will prevent automatic service restarts, regardless of the restart setting configured with Restart=. Exit status definitions can be numeric termination statuses, termination status names, or termination signal names, separated by spaces. Defaults to the empty list, so that, by default, no exit status is excluded from the configured restart logic. A service with the RestartPreventExitStatus= setting RestartPreventExitStatus=TEMPFAIL 250 SIGKILL Exit status 75 (TEMPFAIL), 250, and the termination signal SIGKILL will not result in automatic service restarting. This option may appear more than once, in which case the list of restart-preventing statuses is merged. If the empty string is assigned to this option, the list is reset and all prior assignments of this option will have no effect. Source: systemd v260.1, `systemd.service(5)`. */
   readonly RestartPreventExitStatus?: string | number | readonly (string | number)[];
+  /** Adds a uniformly distributed random delay between zero and this duration to automatic restarts, on top of `RestartSec=` and any exponential backoff configured by `RestartSteps=`/`RestartMaxDelaySec=`. Accepts seconds or a time span string. Defaults to 0, disabling the extra delay. Source: systemd v262, `systemd.service(5)`. */
+  readonly RestartRandomizedDelaySec?: number | string;
   /** Configures the time to sleep before restarting a service (as configured with Restart=). Takes a unit-less value in seconds, or a time span value such as "5min 20s". Defaults to 100ms. Source: systemd v260.1, `systemd.service(5)`. */
   readonly RestartSec?: number | string;
   /** Configures the number of exponential steps to take to increase the interval of auto-restarts from RestartSec= to RestartMaxDelaySec=. Takes a positive integer or 0 to disable it. Defaults to 0. Hint: values between 3 and 5 are good choices when exponential backoff is desired. Source: systemd v260.1, `systemd.service(5)`. */
@@ -905,7 +911,7 @@ interface SystemdServiceSection extends CustomDirectiveSection {
   readonly RestrictNamespaces?: boolean | string | readonly string[];
   /** Takes a list of space-separated network interface names. This option restricts the network interfaces that processes of this unit can use. By default, processes can only use the network interfaces listed (allow-list). If the first character of the rule is ~, the effect is inverted: the processes can only use network interfaces not listed (deny-list). Source: systemd v260.1, `systemd.resource-control(5)`. */
   readonly RestrictNetworkInterfaces?: string | readonly string[];
-  /** If set, any attempts to enable realtime scheduling in a process of the unit are refused. This restricts access to realtime task scheduling policies such as SCHED_FIFO, SCHED_RR or SCHED_DEADLINE. See sched7 for details about these scheduling policies. Realtime scheduling policies may be used to monopolize CPU time for longer periods of time, and may hence be used to lock up or otherwise trigger Denial-of-Service situations on the system. It is hence recommended to restrict access to realtime scheduling to the few programs that actually require them. Defaults to off. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** If set, any attempts to enable realtime scheduling in a process of the unit are refused. This restricts access to realtime task scheduling policies such as SCHED_FIFO, SCHED_RR or SCHED_DEADLINE. See sched7 for details about these scheduling policies. Realtime scheduling policies may be used to monopolize CPU time for longer periods of time, and may hence be used to lock up or otherwise trigger Denial-of-Service situations on the system. It is hence recommended to restrict access to realtime scheduling to the few programs that actually require them. The system call filter cannot inspect the scheduling policy passed to `sched_setattr()`, so that call is blocked entirely, including for non-realtime uses. Defaults to off. Source: systemd v262.1, `systemd.exec(5)`. */
   readonly RestrictRealtime?: boolean;
   /** If set, any attempts to set the set-user-ID (SUID) or set-group-ID (SGID) bits on files or directories will be denied (for details on these bits see inode7). As the SUID/SGID bits are mechanisms to elevate privileges, and allow users to acquire the identity of other users, it is recommended to restrict creation of SUID/SGID files to the few programs that actually require them. Note that this restricts marking of any type of file system object with these bits, including both regular files and directories (where the SGID is a different meaning than for files, see documentation). This option is implied if DynamicUser= is enabled. Seccomp blocks calls with directly supplied mode bits only when SUID or SGID is requested, but blocks calls such as openat2() entirely because their mode bits cannot be inspected. Source: systemd v261.3, `systemd.exec(5)`. */
   readonly RestrictSUIDSGID?: boolean;
@@ -941,7 +947,7 @@ interface SystemdServiceSection extends CustomDirectiveSection {
   readonly RuntimeRandomizedExtraSec?: number | string;
   /** Set the SELinux security context of the executed process. If set, this will override the automated domain transition. However, the policy still needs to authorize the transition. This directive is ignored if SELinux is disabled. If prefixed by -, failing to set the SELinux security context will be ignored, but it is still possible that the subsequent execve() may fail if the policy does not allow the transition for the non-overridden context. This does not affect commands prefixed with +. See setexeccon3 for details. Source: systemd v260.1, `systemd.exec(5)`. */
   readonly SELinuxContext?: string;
-  /** Controls the secure bits set for the executed process. Takes a space-separated combination of options from the following list: keep-caps, keep-caps-locked, no-setuid-fixup, no-setuid-fixup-locked, noroot, and noroot-locked. This option may appear more than once, in which case the secure bits are ORed. If the empty string is assigned to this option, the bits are reset to 0. This does not affect commands prefixed with +. See capabilities(7) for details. Source: systemd v260.1, `systemd.exec(5)`. */
+  /** Sets a space-separated combination of secure bits: `keep-caps`, `no-setuid-fixup`, `noroot`, `no-cap-ambient-raise`, `exec-restrict-file`, `exec-deny-interactive`, and their `-locked` variants. Repeated assignments combine the bits; an empty string resets them to zero. Commands prefixed with `+` are unaffected. See capabilities(7) and the kernel executability-check documentation. Source: systemd v262, `systemd.exec(5)`. */
   readonly SecureBits?: string | readonly string[];
   /** Specifies whether to send SIGHUP to remaining processes immediately after sending the signal configured with KillSignal=. This is useful to indicate to shells and shell-like programs that their connection has been severed. Takes a boolean value. Defaults to no. Source: systemd v260.1, `systemd.kill(5)`. */
   readonly SendSIGHUP?: boolean;
@@ -1069,7 +1075,7 @@ interface SystemdServiceSection extends CustomDirectiveSection {
   readonly UtmpIdentifier?: string;
   /** Takes one of init, login or user. If UtmpIdentifier= is set, controls which type of utmp5/wtmp entries for this service are generated. This setting has no effect unless UtmpIdentifier= is set too. If init is set, only an INIT_PROCESS entry is generated and the invoked process must implement a getty-compatible utmp/wtmp logic. If login is set, first an INIT_PROCESS entry, followed by a LOGIN_PROCESS entry is generated. In this case, the invoked process must implement a login1-compatible utmp/wtmp logic. If user is set, first an INIT_PROCESS entry, then a LOGIN_PROCESS entry and finally a USER_PROCESS entry is generated. In this case, the invoked process may be any process that is suitable to be run as session leader. Defaults to init. Source: systemd v260.1, `systemd.exec(5)`. */
   readonly UtmpMode?: UtmpModeDirectiveValue;
-  /** Configures the mechanism via which the service notifies the manager that the service start-up has finished. One of simple, exec, forking, oneshot, dbus, notify, notify-reload, or idle:. Source: systemd v260.1, `systemd.service(5)`. */
+  /** Configures how the service notifies the manager that startup has finished: `simple`, `exec`, `forking`, `oneshot`, `dbus`, `notify`, `notify-reload`, or `idle`. With `notify-reload`, the main process must catch or block `ReloadSignal=` before sending its initial `READY=1` notification, or startup fails. Source: systemd v262, `systemd.service(5)`. */
   readonly Type?: ServiceTypeDirectiveValue;
   /** Configures the watchdog timeout for a service. The watchdog is activated when the start-up is completed. The service must call sd_notify3 regularly with WATCHDOG=1 (i.e. the "keep-alive ping"). If the time between two such calls is larger than the configured time, then the service is placed in a failed state and it will be terminated with SIGABRT (or the signal specified by WatchdogSignal=). By setting Restart= to on-failure, on-watchdog, on-abnormal or always, the service will be automatically restarted. The time configured here will be passed to the executed service process in the WATCHDOG_USEC= environment variable. This allows daemons to automatically enable the keep-alive pinging logic if watchdog support is enabled for the service. If this option is used, NotifyAccess= (see below) should be set to open access to the notification socket provided by systemd. If NotifyAccess= is not set, it will be implicitly set to main. Defaults to 0, which disables this feature. The service can check whether the service manager expects watchdog keep-alive notifications. See sd_watchdog_enabled3 for details. sd_event_set_watchdog3 may be used to enable automatic watchdog notification support. Source: systemd v260.1, `systemd.service(5)`. */
   readonly WatchdogSec?: number | string;
@@ -1359,6 +1365,10 @@ declare const notify: {
    * Use this when a `Type=notify` service has completed its startup work and is
    * ready to be considered fully started. If `options.status` is provided, it is
    * sent as an additional `STATUS=...` field.
+   *
+   * With `Type=notify-reload`, the main process must catch or block its
+   * `ReloadSignal=` (SIGHUP by default) before sending readiness. Since systemd
+   * v262, startup fails if it does neither. Source: systemd v262, `systemd.service(5)`.
    */
   ready(options?: NotifyOptions): Promise<Result<void, NotifySendError>>;
   /**
@@ -1632,4 +1642,4 @@ declare function defaultSystemd(): Systemd;
 declare const Internal: typeof internal_d_exports;
 //#endregion
 export { SystemdServiceOptions as $, CommandExecutionOptions as A, SystemctlActiveState as B, UnitLogsReadError as C, UnitStartError as D, UnitMaterializationErrorReason as E, MaterializedUnit as F, SystemctlOptions as G, SystemctlIsEnabledOptions as H, NotifyOptions as I, SystemctlStateQueryOptions as J, SystemctlServiceStatus as K, ServiceBaseName as L, CommandOutput as M, ExecutableOptions as N, AnySystemdService as O, LogsOptions as P, SystemdOptions as Q, ServiceFilename as R, UnitEnableError as S, UnitMaterializationError as T, SystemctlIsSystemRunningOptions as U, SystemctlEnablementState as V, SystemctlListTimersOptions as W, SystemctlSystemRunningState as X, SystemctlStatusOptions as Y, SystemctlTimerListEntry as Z, NotifySendErrorReason as _, SystemdTsAttachOptions as a, TimerTargetUnit as at, SystemdCommandEnvironmentReason as b, SystemdTsDetachOptions as c, SystemdTimer as ct, Systemctl as d, defineExecutable as dt, SystemdTimerOptions as et, notify as f, Result as ft, NotifySendError as g, NoUnitsProvidedError as h, SystemdTs as i, TimerTargetServiceName as it, CommandExecutor as j, AnySystemdTimer as k, SystemdTsReattachOptions as l, SystemdService as lt, InvalidExecDirectiveError as m, Systemd as n, TimerBaseName as nt, SystemdTsAttachmentResult as o, UnitValue as ot, ExecutableInferenceError as p, SystemctlShowOptions as q, SystemdMaterialization as r, TimerFilename as rt, SystemdTsAttachmentSelector as s, ValidInstallUnits as st, Internal as t, SystemdUnit as tt, defaultSystemd as u, Executable as ut, SystemctlCommandError as v, UnitLogsReadErrorReason as w, SystemdTsError as x, SystemctlCommandErrorReason as y, StartStatus as z };
-//# sourceMappingURL=index-6lsBWH4h.d.mts.map
+//# sourceMappingURL=index-C9XrvZh3.d.mts.map

package/dist/index-C9XrvZh3.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index-C9XrvZh3.d.mts","names":["I"],"sources":["../src/main/internal.ts","../src/main/executable.ts","../src/main/systemd-service.ts","../src/main/systemd-timer.ts","../src/main/types.ts","../src/main/errors.ts","../src/main/notify.ts","../src/main/systemctl.ts","../src/main/systemd.ts","../src/main/index.ts"],"mappings":";;;KAiBY,OAAO,QAAQ;WAEZ;WACA,OAAO;;WAGP;WACA,OAAO;;KAgBjB;iBAEW,kBAAkB,cAAc;iBAIhC,uBAAuB,SAAS;iBAShC,uBAAuB;iBAQvB,kBAAkB,iBAAiB,wBAAwB,qBACzE,SAAS,WACR,SAAS;iBAUI,iBAAiB,iBAAiB,yBAChD,SAAS,WACR;iBAgBa,uBACd,SAAS,wBACR,aAAa;iBAcA,iBAAiB,cAAc,iBAAiB;iBA4BhD,eACd,UAAU,gCAAgC,4BACzC,eAAe;iBAuDI,uBACpB,iBACA,yBACA,UAAS,0BACR,QAAQ;iBAYW,WAAW,eAAe;iBAS1B,WACpB,iCACA,SAAS,gBACR;iBAmDa,qBAAqB,iBAAiB;;;;;;;;;;;;;;;;cC3PzC;;WAEK;;WAEA,gBAAgB;;WAEhB;;WAEA;;;;;;;;;;;;EAahB,YAAmB,UAAS;;;;;;;EAkBrB,kBAAkB,uCAAuC;;;;;EAkBzD,eAAe,eAAe;;;;;;;;;;;;;;;;;;;;;iBAgCvB,iBACd,iBAAiB,eACjB,UAAS,oBACR;;;;;;;;;;;;;;cCvFU,qBAAqB,iBAAiB,wBAAwB;;WAEzD,SAAS;;WAET,MAAM,gBAAgB;;WAEtB,SAAS,SAAS;;WAElB,SAAS;;WAET,MAAM;;;;;;;;EAStB,YAAmB,SAAS,WAAW,2BAA2B;;MAUvD,YAAY,gBAAgB;;;;;;;;EAWhC,UAAU,eAAe,2BAA2B;;;;;;;;;;;;;;cCvChD,mBAAmB,iBAAiB,sBAAsB;;WAErD,SAAS;;WAET,MAAM,cAAc;;WAEpB,SAAS,SAAS;;WAElB,mBAAmB,uBAAuB;;WAE1C,YAAY,gBAAgB;;WAE5B,OAAO;;WAEP,MAAM;;;;;;;EAQtB,YAAmB,SAAS,WAAW,yBAAyB;;MAiBrD,YAAY,cAAc;;EAK9B,UAAU,eAAe;;;;KCjEtB;KAiBA;KAQA;KASA;KACA;KAQA;KACA;KACA;KACA;KACA;KACA;KACA;KACA;KACA;KACA;KACA;KACA;KAqBA;KASA;KACA;KACA;KACA;KACA;KAKA;KACA;KACA;KACA;KAUA;KAcA,8BAA8B;;KAE9B,yBAAyB,gCAAgC;KACzD,wCAAwC;KACxC,yBAAyB;KACzB,mBAAmB,YAAY;UAE1B;YACL,qBAAqB;;;;;;;;;;;UAYhB,2BAA2B;;WAEjC;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,gBAAgB;;WAEhB;;WAEA;;WAEA;;WAEA,mBAAmB;;WAEnB;;WAEA;;WAEA;;WAEA;;WAEA,mBAAmB;;WAEnB;;WAEA,mBAAmB;;WAEnB;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,mBAAmB;;WAEnB;;WAEA;;WAEA;;WAEA;;WAEA,gBAAgB;;WAEhB;;WAEA;;WAEA;;WAEA;;WAEA;;;;;;;;;UAUM,8BAA8B;;WAEpC;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;;;;;;;UASM,4BAA4B;;WAElC;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;;;;;;;;UAUM,8BAA8B;;WAEpC;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,kBAAkB;;WAElB,sBAAsB;;WAEtB;;WAEA;;WAEA;;WAEA,mBAAmB;;WAEnB;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,eAAe;;WAEf;;WAEA;;WAEA;;WAEA;;WAEA,gBAAgB;;WAEhB;;WAEA,aAAa;;WAEb,iBAAiB;;WAEjB;;WAEA,YAAY;;WAEZ,gBAAgB;;WAEhB,eAAe;;WAEf,WAAW;;WAEX,eAAe;;WAEf,WAAW;;WAEX;;WAEA;;WAEA;;WAEA;;WAEA,8BAA8B;;WAE9B,kBAAkB,OAAO;;WAEzB;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,oBAAoB;;WAEpB;;WAEA;;WAEA;;WAEA,kBAAkB;;WAElB;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,cAAc;;WAEd;;WAEA,aAAa,OAAO;;WAEpB,UAAU;;WAEV,YAAY;;WAEZ,WAAW;;WAEX,YAAY;;WAEZ,aAAa;;WAEb,aAAa;;WAEb,eAAe;;WAEf,gBAAgB;;WAEhB,YAAY;;WAEZ,cAAc;;WAEd,aAAa;;WAEb,WAAW;;WAEX,cAAc;;WAEd,cAAc;;WAEd,kBAAkB;;WAElB,aAAa;;WAEb;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,cAAc;;WAEd;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,2BAA2B;;WAE3B;;WAEA;;WAEA,uBAAuB;;WAEvB,iBAAiB;;WAEjB;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,sBAAsB;;WAEtB;;WAEA,YAAY;;WAEZ;;WAEA;;WAEA;;WAEA,aAAa;;WAEb;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,eAAe;;WAEf,YAAY;;WAEZ;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,aAAa;;WAEb;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,cAAc;;WAEd;;WAEA;;WAEA;;WAEA;;WAEA,eAAe,OAAO;;WAEtB;;WAEA;;WAEA,UAAU;;WAEV;;WAEA,oBAAoB,OAAO;;WAE3B;;WAEA,cAAc;;WAEd;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,gBAAgB;;WAEhB,gBAAgB;;WAEhB;;WAEA;;WAEA,iBAAiB;;WAEjB;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,iBAAiB;;WAEjB;;WAEA,cAAc;;WAEd;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,0BAA0B;;WAE1B;;WAEA,yBAAyB;;WAEzB;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA;;WAEA,WAAW;;WAEX,OAAO;;WAEP;;WAEA,iBAAiB,OAAO;;WAExB;;UAGM;WACN,UAAU;WACV;WACA,SAAS;WACT,OAAO;;UAGD;WACN,UAAU;WACV;WACA,OAAO;WACP,OAAO;;KAGb,YAAY,SAAS,UAAU,sBACxB,KAAK,cAAc,eAAe;KAGzC,qBAAqB,UAAU,UAAU,yCAE1C,YAAY,UAAU;KAEd,2BAA2B,iBAAiB,yBAAyB,YAC/E,KAAK;WACM,UAAU,qBAAqB,qBAAqB;WACpD,SAAS,YAAY,qBAAqB;WAC1C,OAAO,qBAAqB,kBAAkB;GAEzD;KAGU,yBAAyB,iBAAiB,uBAAuB,YAC3E,KAAK;WACM,UAAU,qBAAqB,qBAAqB;WACpD,OAAO,YAAY,mBAAmB;WACtC,OAAO,qBAAqB,kBAAkB;GAEzD;UAGe;WACN,WAAW;WACX;WACA;WACA;;UAGM;WACN,WAAW;WACX;;KAGC;KAiBA;UAUK;WACN;WACA;;UAGM;WACN,MAAM,SAAS;;KAGd,mBACV,iBACA,yBACA,UAAU,4BACP,QAAQ;UAEI;WACN;;UAGM;WACN;;UAGM;WACN;WACA;;UAGM;WACN;WACA;WACA;;;;;;;;;UAUM;WACN;WACA;WACA;WACA;WACA;WACA;;UAGM;WACN;WACA;;UAGM;WACN;;UAGM;WACN;;KAGC;UAUK;WACN,WAAW;WACX;WACA;WACA;;UAGM;WACN;WACA;WACA;WACA;WACA;;;;;;;;UASM,+BAA+B;UAE/B;WACN;WACA;WACA;;KAGC,gBACV,sBACA,yBACE,uBAAuB,OAAO,WAAW,OAAO;KAExC,gBAAgB,wBAAwB,gBAAgB;KACxD,cAAc,wBAAwB,gBAAgB;KACtD,gBAAgB,2BAA2B,gBAAgB;KAC3D,cAAc,2BAA2B,cAAc;KAEvD,gBAAgB,iBAAiB,uBAAuB;WACzD,YAAY;IAEnB,WACA,gBAAgB;KAER,uBAAuB,iBAAiB,uBAClD,gBAAgB,2BAA2B,iBAAiB;KAEzD,aAAa,uCAAuC;KAE7C,oBAAoB,eAAe;KACnC,kBAAkB,aAAa;KAC/B,cAAc,oBAAoB;UAE7B,iBAAiB,cAAc,cAAc;WACnD;WACA,MAAM;;KAGZ,eAAe,wBAAwB,iBAAiB,8BAA6B,SACtF,cAAc,oBACZ;KAID,uBAAuB,eAAe,iBAAiB,gCAC1D,aAAa,uBAAuB,0CAEhC,aAAa,sCAEV,QAAQ,eAAe,uBAAuB;KAIlD,iBAAiB,wBAAwB,iBAAiB,8BAA6B,SACxF,cAAc,kBACZ,uBAAuB,OAAO,eAAe,gCAE3C;KAIH,YAAY,wBAAwB,kBAAkB,eAAe;KAIrE,+BAA+B,wBAAwB,iBAC1D,YAAY,wBACP,iBAAiB;KAKZ,kBAAkB,wBAAwB,iBACpD,+BAA+B,+BAA+B;;;KC3uCpD;UAWK;WACN;;UAGM,mCAAmC;WACzC;WACA;WACA,oBAAoB;WACpB;WACA;WACA;;UAGM;WACN;WACA,aAAa;WACb;;UAGM,8BAA8B;WACpC,cAAc;;UAGR,wCAAwC;WAC9C,SAAS;WACT;WACA;WACA;;KAGC;UAKK,iCAAiC;WACvC,SAAS;WACT;;KAGC;UAKK,+BAA+B;WACrC,SAAS;;KAGR;UAEK,qCAAqC;WAC3C;WACA,SAAS;;KAGR;KAEA;cAKC,uBAAuB;WAClB,MAAM;EAEtB,YACE,MAAM,oBACN,iBACA,UAAS;;cAQA,kCAAkC;WAC7B;EAEhB,YAAmB,mBAAmB,UAAS;;cAUpC,6BAA6B;WACxB;EAEhB,YAAmB,mBAAmB,UAAS;;cAUpC,iCAAiC;EAC5C,YAAmB,UAAS;;cASjB,iCAAiC;WAC5B;WACA,QAAQ;WACR;WACA;EAEhB,YAAmB,iBAAiB,UAAS;;cASlC,wBAAwB;WACnB;WACA;WACA,mBAAmB;WACnB;WACA;WACA;WACA;WACA;WACA;EAEhB,YAAmB,iBAAiB,UAAS;;cAgBlC,uBAAuB;WAClB;WACA;WACA,aAAa;WACb,mBAAmB;WACnB;WACA;WACA;WACA;WACA;WACA;EAEhB,YAAmB,iBAAiB,UAAS;;cAiBlC,0BAA0B;WACrB;WACA;WACA,mBAAmB;WACnB;WACA,QAAQ;WACR;WACA;WACA;WACA;WACA;EAEhB,YAAmB,iBAAiB,UAAS;;cAiBlC,wBAAwB;WACnB;WACA;WACA,mBAAmB;WACnB;WACA,QAAQ;WACR;WACA;WACA;EAEhB,YAAmB,iBAAiB,UAAS;;cAelC,8BAA8B;WACzB;WACA;WACA,mBAAmB;WACnB;WACA;WACA,QAAQ;WACR;WACA;WACA;EAEhB,YAAmB,iBAAiB,UAAS;;;;;;;;;;;;;;;;cCtPlC;;;;;;;;;;;;EAYL,MAAK,UAAU,gBAAqB,QAAQ,aAAa;;;;;;;;EAyBzD,SAAQ,UAAU,gBAAqB,QAAQ,aAAa;;;;;;;;;;;cCzBvD;;WAEK,UAAU;;WAEV;EAEhB,YAAmB,UAAS;;EAOf,gBAAgB,QAAQ,OAAO,eAAe;;EAK9C,OAAO,eAAe,QAAQ,OAAO,eAAe;;EAKpD,QAAQ,eAAe,QAAQ,OAAO,eAAe;;EAKrD,KAAK,eAAe,QAAQ,OAAO,eAAe;;;;;;;EAUlD,UACX,cACA,UAAS,4BACR,QAAQ,OAAO,0BAA0B;;;;;;;EAmB/B,SACX,cACA,UAAS,6BACR,QAAQ,OAAO,sBAAsB;;;;;;;EAc3B,SACX,cACA,UAAS,6BACR,QAAQ,OAAO,sBAAsB;;;;;;;EAc3B,gBACX,UAAS,kCACR,QAAQ,OAAO,6BAA6B;;;;;;EAalC,KACX,cACA,UAAS,uBACR,QAAQ,OAAO,eAAe;;;;;;EAapB,eACX,cACA,UAAS,uBACR,QAAQ,OAAO,SAAS,yBAAyB;;;;;EAYvC,WAAW,eAAe,QAAQ,OAAO,aAAa;;;;;EAQtD,kBACX,eACC,QAAQ,OAAO,wBAAwB;;;;;EAc7B,WACX,UAAS,6BACR,QAAQ,gBAAgB,2BAA2B;;EA4BzC,MAAM,eAAe,QAAQ,OAAO,eAAe;;EAKnD,KAAK,eAAe,QAAQ,OAAO,eAAe;;EAKlD,QAAQ,eAAe,QAAQ,OAAO,eAAe;;;;;EAQrD,YACX,+BACC,QAAQ,OAAO,eAAe;;;;;;;EAUpB,OACX,cACA,UAAS,yBACR,QAAQ,OAAO,eAAe;;EAapB,OACR,0BACF,QAAQ,OAAO,eAAe;UAiBzB;;;;UC7PO;WACN;WACA;WACA;;UAGM;WACN;WACA;WACA;;UAGM,iCAAiC;WACvC;WACA;WACA;WACA;;UAGM;WACN;;UAGM;WACN;WACA;WACA;WACA;WACA;WACA;WACA;WACA;WACA;WACA;;;;;;;;cAkBE,uBACX,wBAAwB,yBAAyB;;WAGjC;;WAEA,uBAAuB,iBAAiB;EAExD,YAAmB,mBAAmB,uBAAuB,iBAAiB;;;;;;;;;;;;cAiBnE;;WAEK,UAAU;;WAEV;;WAEA;;WAEA,WAAW;;WAEX,IAAI;;WAEJ;;;;;;;;EAShB,YAAmB,UAAS;;;;;;;EAmBf,kBAAkB,wBAAwB,kBAClD,OAAO,SAAS,kBAAkB,UACpC,QACD,OACE,uBAAuB,SACrB,2BACA,4BACA,uBACA;;;;;;;;EAaO,UACR,gBAAgB,gBAClB,QAAQ,aAAa,uBAAuB;;;;;;;;EAkDlC,MAAM,MAAM,cAAc,QAAQ,OAAO,aAAa;;;;;;;;EAoEtD,KACX,MAAM,aACN,UAAU,cACT,QAAQ,eAAe;;EAsDnB,QAAQ,MAAM;UAIP;UAiDN;UAIM;UA2CA;UAiBA;UA4DA;;;;;;;;;cA6BH;mBACM;EAEjB,YAAmB,SAAS;EAKf,OACX,gBAAgB,eAChB,SAAS,yBACR,QACD,OACE,2BACE,2BACA,4BACA,uBACA,kBACA,2BACA;EAwDO,OACX,UAAU,6BACV,UAAS,yBACR,QACD;aAEa;aACA;aACA;aACA;aACA;KAEX;EA+CS,SACX,gBAAgB,eAChB,SAAS,2BACR,QACD,OACE,2BACE,2BACA,4BACA,uBACA,kBACA,2BACA,iBACA;UA0FQ;UA0BA;UAiDA;UAMN;UAIM;UASA;UAQA;UAIN;UAIM;;;;;;;;iBAyCA,kBAAkB;;;;;;;cCl2BrB,iBAAiBA"}

package/dist/index.d.mts

@@ -1,2 +1,2 @@
-import { $ as SystemdServiceOptions, A as CommandExecutionOptions, B as SystemctlActiveState, C as UnitLogsReadError, D as UnitStartError, E as UnitMaterializationErrorReason, F as MaterializedUnit, G as SystemctlOptions, H as SystemctlIsEnabledOptions, I as NotifyOptions, J as SystemctlStateQueryOptions, K as SystemctlServiceStatus, L as ServiceBaseName, M as CommandOutput, N as ExecutableOptions, O as AnySystemdService, P as LogsOptions, Q as SystemdOptions, R as ServiceFilename, S as UnitEnableError, T as UnitMaterializationError, U as SystemctlIsSystemRunningOptions, V as SystemctlEnablementState, W as SystemctlListTimersOptions, X as SystemctlSystemRunningState, Y as SystemctlStatusOptions, Z as SystemctlTimerListEntry, _ as NotifySendErrorReason, a as SystemdTsAttachOptions, at as TimerTargetUnit, b as SystemdCommandEnvironmentReason, c as SystemdTsDetachOptions, ct as SystemdTimer, d as Systemctl, dt as defineExecutable, et as SystemdTimerOptions, f as notify, ft as Result, g as NotifySendError, h as NoUnitsProvidedError, i as SystemdTs, it as TimerTargetServiceName, j as CommandExecutor, k as AnySystemdTimer, l as SystemdTsReattachOptions, lt as SystemdService, m as InvalidExecDirectiveError, n as Systemd, nt as TimerBaseName, o as SystemdTsAttachmentResult, ot as UnitValue, p as ExecutableInferenceError, q as SystemctlShowOptions, r as SystemdMaterialization, rt as TimerFilename, s as SystemdTsAttachmentSelector, st as ValidInstallUnits, t as Internal, tt as SystemdUnit, u as defaultSystemd, ut as Executable, v as SystemctlCommandError, w as UnitLogsReadErrorReason, x as SystemdTsError, y as SystemctlCommandErrorReason, z as StartStatus } from "./index-6lsBWH4h.mjs";
+import { $ as SystemdServiceOptions, A as CommandExecutionOptions, B as SystemctlActiveState, C as UnitLogsReadError, D as UnitStartError, E as UnitMaterializationErrorReason, F as MaterializedUnit, G as SystemctlOptions, H as SystemctlIsEnabledOptions, I as NotifyOptions, J as SystemctlStateQueryOptions, K as SystemctlServiceStatus, L as ServiceBaseName, M as CommandOutput, N as ExecutableOptions, O as AnySystemdService, P as LogsOptions, Q as SystemdOptions, R as ServiceFilename, S as UnitEnableError, T as UnitMaterializationError, U as SystemctlIsSystemRunningOptions, V as SystemctlEnablementState, W as SystemctlListTimersOptions, X as SystemctlSystemRunningState, Y as SystemctlStatusOptions, Z as SystemctlTimerListEntry, _ as NotifySendErrorReason, a as SystemdTsAttachOptions, at as TimerTargetUnit, b as SystemdCommandEnvironmentReason, c as SystemdTsDetachOptions, ct as SystemdTimer, d as Systemctl, dt as defineExecutable, et as SystemdTimerOptions, f as notify, ft as Result, g as NotifySendError, h as NoUnitsProvidedError, i as SystemdTs, it as TimerTargetServiceName, j as CommandExecutor, k as AnySystemdTimer, l as SystemdTsReattachOptions, lt as SystemdService, m as InvalidExecDirectiveError, n as Systemd, nt as TimerBaseName, o as SystemdTsAttachmentResult, ot as UnitValue, p as ExecutableInferenceError, q as SystemctlShowOptions, r as SystemdMaterialization, rt as TimerFilename, s as SystemdTsAttachmentSelector, st as ValidInstallUnits, t as Internal, tt as SystemdUnit, u as defaultSystemd, ut as Executable, v as SystemctlCommandError, w as UnitLogsReadErrorReason, x as SystemdTsError, y as SystemctlCommandErrorReason, z as StartStatus } from "./index-C9XrvZh3.mjs";
 export { type AnySystemdService, type AnySystemdTimer, type CommandExecutionOptions, type CommandExecutor, type CommandOutput, Executable, ExecutableInferenceError, type ExecutableOptions, Internal, InvalidExecDirectiveError, type LogsOptions, type MaterializedUnit, NoUnitsProvidedError, type NotifyOptions, NotifySendError, type NotifySendErrorReason, type Result, type ServiceBaseName, type ServiceFilename, type StartStatus, Systemctl, type SystemctlActiveState, SystemctlCommandError, type SystemctlCommandErrorReason, type SystemctlEnablementState, type SystemctlIsEnabledOptions, type SystemctlIsSystemRunningOptions, type SystemctlListTimersOptions, type SystemctlOptions, type SystemctlServiceStatus, type SystemctlShowOptions, type SystemctlStateQueryOptions, type SystemctlStatusOptions, type SystemctlSystemRunningState, type SystemctlTimerListEntry, Systemd, type SystemdCommandEnvironmentReason, SystemdMaterialization, type SystemdOptions, SystemdService, type SystemdServiceOptions, SystemdTimer, type SystemdTimerOptions, SystemdTs, type SystemdTsAttachOptions, type SystemdTsAttachmentResult, type SystemdTsAttachmentSelector, type SystemdTsDetachOptions, SystemdTsError, type SystemdTsReattachOptions, type SystemdUnit, type TimerBaseName, type TimerFilename, type TimerTargetServiceName, type TimerTargetUnit, UnitEnableError, UnitLogsReadError, type UnitLogsReadErrorReason, UnitMaterializationError, type UnitMaterializationErrorReason, UnitStartError, type UnitValue, type ValidInstallUnits, defaultSystemd, defineExecutable, notify };

package/dist/index.mjs

@@ -1,2 +1 @@
-import { _ as SystemdTsError, a as defaultSystemd, b as UnitMaterializationError, c as SystemdService, d as defineExecutable, f as ExecutableInferenceError, g as SystemctlCommandError, h as NotifySendError, i as SystemdTs, l as notify, m as NoUnitsProvidedError, n as Systemd, o as Systemctl, p as InvalidExecDirectiveError, r as SystemdMaterialization, s as SystemdTimer, t as Internal, u as Executable, v as UnitEnableError, x as UnitStartError, y as UnitLogsReadError } from "./main-DqJ5f7Al.mjs";
-export { Executable, ExecutableInferenceError, Internal, InvalidExecDirectiveError, NoUnitsProvidedError, NotifySendError, Systemctl, SystemctlCommandError, Systemd, SystemdMaterialization, SystemdService, SystemdTimer, SystemdTs, SystemdTsError, UnitEnableError, UnitLogsReadError, UnitMaterializationError, UnitStartError, defaultSystemd, defineExecutable, notify };
+export { u as Executable, f as ExecutableInferenceError, t as Internal, p as InvalidExecDirectiveError, m as NoUnitsProvidedError, h as NotifySendError, o as Systemctl, g as SystemctlCommandError, n as Systemd, r as SystemdMaterialization, c as SystemdService, s as SystemdTimer, i as SystemdTs, _ as SystemdTsError, v as UnitEnableError, y as UnitLogsReadError, b as UnitMaterializationError, x as UnitStartError, a as defaultSystemd, d as defineExecutable, l as notify } from "./main-BlzhT1eg.mjs";

package/dist/{main-DqJ5f7Al.mjs → main-BlzhT1eg.mjs}

@@ -601,6 +601,10 @@ const notify = {
 	* Use this when a `Type=notify` service has completed its startup work and is
 	* ready to be considered fully started. If `options.status` is provided, it is
 	* sent as an additional `STATUS=...` field.
+	*
+	* With `Type=notify-reload`, the main process must catch or block its
+	* `ReloadSignal=` (SIGHUP by default) before sending readiness. Since systemd
+	* v262, startup fails if it does neither. Source: systemd v262, `systemd.service(5)`.
 	*/
 	async ready(options = {}) {
 		try {
@@ -1609,4 +1613,4 @@ const Internal = internal_exports;
 //#endregion
 export { SystemdTsError as _, defaultSystemd as a, UnitMaterializationError as b, SystemdService as c, defineExecutable as d, ExecutableInferenceError as f, SystemctlCommandError as g, NotifySendError as h, SystemdTs as i, notify as l, NoUnitsProvidedError as m, Systemd as n, Systemctl as o, InvalidExecDirectiveError as p, SystemdMaterialization as r, SystemdTimer as s, Internal as t, Executable as u, UnitEnableError as v, UnitStartError as x, UnitLogsReadError as y };
 
-//# sourceMappingURL=main-DqJ5f7Al.mjs.map
+//# sourceMappingURL=main-BlzhT1eg.mjs.map