テーマ： services
-
FreeBSD の rc.conf、sysrc、service：有効化、起動、起動時に動くものの確認
FreeBSD のサービスは rc.conf の変数で宣言的に有効化する。変数は /etc/rc.conf または /etc/rc.conf.d のサービス別ファイルに置く。sysrc と service <name> enable はどちらも変数を書くだけで、rc.conf 自体は直接何かを実行するものではなく、/etc/rc.d の rc スクリプトが読む変数を設定する。sysrc はスクリプトから変数を安全に編集し、service は対応する rc.d スクリプトを起動・停止して状態を報告する。
-
Reading and changing service state with the Service Management Facility: svcs and svcadm
SMF is the Solaris equivalent of systemd unit management. svcs -a/-x/-l read state and find problems, svcadm enable/disable/restart/refresh change it, -t makes a change temporary, and svcadm clear recovers an instance stuck in maintenance.
-
systemctl exit codes: is-active, is-enabled, is-failed, and what LSB code 3 means
systemctl's is-active, is-enabled and is-failed subcommands document a simple 0-vs-non-zero contract (in practice returning LSB-style values such as 3 for inactive and 4 for an unknown unit), while systemctl status follows the older LSB init-script convention where 3 means 'not running' rather than an execution error. Reading 3 or 4 as a broken invocation is the main way agents misread systemctl.
-
Managing AIX services with the System Resource Controller: lssrc, startsrc/stopsrc, and rc.tcpip
AIX manages long-running daemons through the System Resource Controller (SRC), a subsystem/group model configured in the ODM's SRCsubsys object class, not systemd units. lssrc/startsrc/stopsrc drive it interactively, while /etc/inittab and scripts like rc.tcpip control what starts automatically at boot.
-
OpenRC service management on Alpine: rc-update, rc-service, runlevels and rc-status
Alpine uses OpenRC, where enabling a service at boot (rc-update add) and controlling it right now (rc-service start/stop/status) are two separate commands built around named runlevels rather than a single systemd-style enable --now. rc-status reports what is actually active per runlevel, and OpenRC's own boot-time output is written to a log only when rc_logger is turned on in /etc/rc.conf.
-
Service startup type and crash recovery: Set-Service plus sc.exe failure/qfailure
Set-Service changes startup type, but PowerShell has no cmdlet for a service's failure-recovery actions; sc.exe failure and sc.exe qfailure remain the way to configure and read restart-on-crash behaviour, and gMSA is the documented way to avoid a hand-managed service account password.
機械可読： JSON