Linux systemd单元启动配置及日志之basic.target

systemd-ask-password-plymouth.service
systemd-ask-password-plymouth.path

    Forward Password Requests to Plymouth Directory Watch
    Documentation=http://www.freedesktop.org/wiki/Software/systemd/PasswordAgents
    
    # journalctl -b -u systemd-ask-password-plymouth.path
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 10:47:01 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.

path.path

    A unit configuration file whose name ends in ".path" encodes information about a path monitored by systemd, for path-based activation.
    For each path file, a matching unit file must exist, describing the unit to activate when the path changes. 
    By default, a service by the same name as the path (except for the suffix) is activated. Example: a path file foo.path activates a matching service foo.service.
    
    Path files must include a [Path] section, which carries information about the path(s) it monitors.
        PathExists=, PathExistsGlob=, PathChanged=, PathModified=, DirectoryNotEmpty=
        Unit=
        MakeDirectory=
        DirectoryMode=

paths.target
● ├─acpid.path
● ├─apport-autoreport.path
● ├─cups.path
● ├─systemd-ask-password-console.path
● └─systemd-ask-password-wall.path

acpid.path
acpid.service

    # journalctl -b -u acpid.path
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 10:50:24 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Started ACPI Events Check.
    
    # journalctl -b -u acpid.service
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 10:50:24 CST. --
    9月 26 09:17:39 eric-vm-dev systemd[1]: Started ACPI event daemon.
    9月 26 09:17:40 eric-vm-dev acpid[1092]: starting up with netlink and the input layer
    9月 26 09:17:41 eric-vm-dev acpid[1092]: 8 rules loaded
    9月 26 09:17:41 eric-vm-dev acpid[1092]: waiting for events: event logging is off

apport-autoreport.path
apport-autoreport.service

    # journalctl -b -u apport-autoreport.path
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:04:56 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Started Process error reports when automatic reporting is enabled (file watch).

cpus.path
cpus.service

    # journalctl -b -u cups.path
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:04:56 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Started CUPS Scheduler.
    9月 26 09:22:33 eric-vm-dev systemd[1]: Stopped CUPS Scheduler.
    9月 26 09:22:33 eric-vm-dev systemd[1]: Stopping CUPS Scheduler.

slice.slice

    A slice unit is a concept for hierarchically managing resources of a group of processes. 
    This management is performed by creating a node in the Linux Control Group (cgroup) tree.

slices.target
● ├─-.slice
● ├─system.slice
● └─user.slice

socket.socket

    A unit configuration file whose name ends in ".socket" encodes information about an IPC or network socket or a file system FIFO controlled and supervised by systemd, for socket-based activation.
    For each socket file, a matching service file must exist, describing the service to start on incoming traffic on the socket.
    The name of the .service unit is by default the same as the name of the .socket unit, but can be altered with the Service= option described below. 
    Depending on the setting of the Accept= option described below, this .service unit must either be named like the .socket unit, but with the suffix replaced, unless overridden with Service=; or it must be a template unit named the same way.
    Example: 
        a socket file foo.socket needs a matching service foo.service if Accept=false is set. 
        If Accept=true is set, a service template file foo@.service must exist from which services are instantiated for each incoming connection.
    
    Socket files must include a [Socket] section, which carries information about the socket or FIFO it supervises.
         ListenStream=, ListenDatagram=, ListenSequentialPacket=
         Specifies an address to listen on for a stream (SOCK_STREAM), datagram (SOCK_DGRAM), or sequential packet (SOCK_SEQPACKET) socket, respectively.
         
         Accept=
         Takes a boolean argument. If true, a service instance is spawned for each incoming connection and only the connection socket is passed to it. 
         If false, all listening sockets themselves are passed to the started service unit, and only one service unit is spawned for all connections. 
         This value is ignored for datagram sockets and FIFOs where a single service unit unconditionally handles all incoming traffic. Defaults to false.
         ......

sockets.target
● ├─acpid.socket
● ├─apport-forward.socket
● ├─avahi-daemon.socket
● ├─cups.socket
● ├─dbus.socket
● ├─docker.socket
● ├─snapd.socket
● ├─syslog.socket
● ├─systemd-initctl.socket
● ├─systemd-journald-audit.socket
● ├─systemd-journald-dev-log.socket
● ├─systemd-journald.socket
● ├─systemd-udevd-control.socket
● ├─systemd-udevd-kernel.socket
● └─uuidd.socket

avahi-daemon.socket
avahi-daemon.service

    # journalctl -b -u avahi-daemon.socket
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:04:56 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
    
    # journalctl -b -u avahi-daemon.service
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:04:56 CST. --
    9月 26 09:17:39 eric-vm-dev systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
    9月 26 09:17:40 eric-vm-dev avahi-daemon[1093]: Found user 'avahi' (UID 116) and group 'avahi' (GID 122).
    9月 26 09:17:40 eric-vm-dev avahi-daemon[1093]: Successfully dropped root privileges.
    9月 26 09:17:40 eric-vm-dev avahi-daemon[1093]: avahi-daemon 0.7 starting up.
    9月 26 09:17:40 eric-vm-dev systemd[1]: Started Avahi mDNS/DNS-SD Stack.
    9月 26 09:17:40 eric-vm-dev avahi-daemon[1093]: Successfully called chroot().
    9月 26 09:17:40 eric-vm-dev avahi-daemon[1093]: Successfully dropped remaining capabilities.
    9月 26 09:17:41 eric-vm-dev avahi-daemon[1093]: No service file found in /etc/avahi/services.
    9月 26 09:17:41 eric-vm-dev avahi-daemon[1093]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
    9月 26 09:17:41 eric-vm-dev avahi-daemon[1093]: New relevant interface lo.IPv6 for mDNS.
    9月 26 09:17:41 eric-vm-dev avahi-daemon[1093]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
    9月 26 09:17:41 eric-vm-dev avahi-daemon[1093]: New relevant interface lo.IPv4 for mDNS.
    9月 26 09:17:41 eric-vm-dev avahi-daemon[1093]: Network interface enumeration completed.
    9月 26 09:17:41 eric-vm-dev avahi-daemon[1093]: Registering new address record for ::1 on lo.*.
    9月 26 09:17:41 eric-vm-dev avahi-daemon[1093]: Registering new address record for 127.0.0.1 on lo.IPv4.

cups.socket

    # journalctl -b -u cups.socket
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:04:56 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Listening on CUPS Scheduler.
    9月 26 09:22:33 eric-vm-dev systemd[1]: Closed CUPS Scheduler.
    9月 26 09:22:33 eric-vm-dev systemd[1]: Stopping CUPS Scheduler.

dbus.socket
dbus.service

    # journalctl -b -u dbus.socket
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:04:56 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Listening on D-Bus System Message Bus Socket.
    
    # journalctl -b -u dbus.service
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:04:56 CST. --
    9月 26 09:17:36 eric-vm-dev systemd[1]: Started D-Bus System Message Bus.
    9月 26 09:17:38 eric-vm-dev dbus-daemon[906]: dbus[906]: Unknown group "power" in message bus configuration file
    9月 26 09:17:39 eric-vm-dev dbus-daemon[906]: [system] AppArmor D-Bus mediation is enabled
    9月 26 09:17:39 eric-vm-dev dbus-daemon[906]: [system] Successfully activated service 'org.freedesktop.systemd1'
    ......

docker.socket
docker.service

    # journalctl -b -u docker.socket
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:04:56 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Starting Docker Socket for the API.
    9月 26 09:17:34 eric-vm-dev systemd[1]: Listening on Docker Socket for the API.

systemd-journald.socket
systemd-journald.service

    # journalctl -b -u systemd-journald.service
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:17:01 CST. --
    9月 26 09:17:11 eric-vm-dev systemd-journald[353]: Journal started
    9月 26 09:17:11 eric-vm-dev systemd-journald[353]: Runtime journal (/run/log/journal/266fb8dd63684e13990aaa34604dc5c8) is 2.4M, max 19.6M, 17.2M free.
    9月 26 09:17:12 eric-vm-dev systemd-journald[353]: Time spent on flushing to /var is 1.672395s for 1578 entries.
    9月 26 09:17:12 eric-vm-dev systemd-journald[353]: System journal (/var/log/journal/266fb8dd63684e13990aaa34604dc5c8) is 720.1M, max 4.0G, 3.2G free.

uuidd.socket

    # journalctl -b -u uuidd.socket
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:18:07 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Listening on UUID daemon activation socket.

timers.timer

    A unit configuration file whose name ends in ".timer" encodes information about a timer controlled and supervised by systemd, for timer-based activation.
    For each timer file, a matching unit file must exist, describing the unit to activate when the timer elapses. 
    By default, a service by the same name as the timer (except for the suffix) is activated. 
    Example: a timer file foo.timer activates a matching service foo.service. The unit to activate may be controlled by Unit=.
    
    Timer files must include a [Timer] section, which carries information about the timer it defines.
        OnActiveSec=, OnBootSec=, OnStartupSec=, OnUnitActiveSec=, OnUnitInactiveSec=
        OnCalendar=
        Unit=
            The unit to activate when this timer elapses. The argument is a unit name, whose suffix is not ".timer".
        RemainAfterElapse=
            If true, an elapsed timer will stay loaded, and its state remains queriable. If false, an elapsed timer unit that cannot elapse anymore is unloaded. 
            Turning this off is particularly useful for transient timer units that shall disappear after they first elapse.
            Note that this setting has an effect on repeatedly starting a timer unit that only elapses once: 
            if RemainAfterElapse= is on, it will not be started again, and is guaranteed to elapse only once. 
            However, if RemainAfterElapse= is off, it might be started again if it is already elapsed, and thus be triggered multiple times. Defaults to yes.
        ......

timers.target
● ├─anacron.timer
● ├─apt-daily-upgrade.timer
● ├─apt-daily.timer
● ├─fstrim.timer
● ├─motd-news.timer
● ├─snapd.snap-repair.timer
● └─systemd-tmpfiles-clean.timer

anacron.timer
anacron.service

    # journalctl -b -u anacron.timer
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:18:07 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Started Trigger anacron every hour.
    
    # journalctl -b -u anacron.service
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:18:07 CST. --
    9月 26 09:17:35 eric-vm-dev systemd[1]: Started Run anacron jobs.
    9月 26 09:17:35 eric-vm-dev anacron[836]: Anacron 2.3 started on 2021-09-26
    9月 26 09:17:35 eric-vm-dev anacron[836]: Will run job `cron.daily' in 5 min.
    9月 26 09:17:35 eric-vm-dev anacron[836]: Jobs will be executed sequentially
    9月 26 09:22:32 eric-vm-dev anacron[836]: Job `cron.daily' started
    9月 26 09:22:32 eric-vm-dev anacron[3014]: Updated timestamp for job `cron.daily' to 2021-09-26
    9月 26 09:22:32 eric-vm-dev cracklib[3042]: no dictionary update necessary.
    ...

fstrim.timer
fstrim.service

    # journalctl -b -u fstrim.timer
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:18:07 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Started Discard unused blocks once a week.
    
    # journalctl -b -u fstrim.service
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:18:07 CST. --
    9月 27 00:00:25 eric-vm-dev systemd[1]: Starting Discard unused blocks...
    9月 27 00:00:25 eric-vm-dev systemd[1]: Started Discard unused blocks.

motd-news.timer
motd-news.service

    # journalctl -b -u motd-news.timer
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:18:07 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Started Message of the Day.

systemd-tmpfiles-clean.timer
systemd-tmpfiles-clean.service

    # journalctl -b -u systemd-tmpfiles-clean.timer
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:18:07 CST. --
    9月 26 09:17:34 eric-vm-dev systemd[1]: Started Daily Cleanup of Temporary Directories.
    
    # journalctl -b -u systemd-tmpfiles-clean.service
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 11:18:07 CST. --
    9月 26 09:32:35 eric-vm-dev systemd[1]: Starting Cleanup of Temporary Directories...
    9月 26 09:32:35 eric-vm-dev systemd[1]: Started Cleanup of Temporary Directories.
    ......