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

accounts-daemon.service

    Description=Accounts Service
    Type=dbus
    BusName=org.freedesktop.Accounts
    ExecStart=/usr/lib/accountsservice/accounts-daemon
    
    # journalctl -b -u accounts-daemon.service
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 13:17:01 CST. --
    9月 26 09:17:36 eric-vm-dev systemd[1]: Starting Accounts Service...
    9月 26 09:17:48 eric-vm-dev accounts-daemon[902]: started daemon version 0.6.45
    9月 26 09:17:48 eric-vm-dev systemd[1]: Started Accounts Service.

gdm.service

    Description=GNOME Display Manager
    ExecStartPre=/usr/share/gdm/generate-config
    ExecStart=/usr/sbin/gdm3
    
    # journalctl -b -u gdm.service
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 13:17:01 CST. --
    9月 26 09:17:50 eric-vm-dev systemd[1]: Starting GNOME Display Manager...
    9月 26 09:17:52 eric-vm-dev systemd[1]: Started GNOME Display Manager.
    9月 26 09:17:57 eric-vm-dev gdm-launch-environment][1515]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)

udisks2.service

    Description=Disk Manager
    provides interfaces to enumerate and perform operations on disks and storage devices.
    Type=dbus
    BusName=org.freedesktop.UDisks2
    ExecStart=/usr/lib/udisks2/udisksd
    
    # journalctl -b -u udisks2.service
    -- Logs begin at Mon 2019-06-03 16:58:43 CST, end at Wed 2021-09-29 13:17:01 CST. --
    9月 26 09:17:35 eric-vm-dev systemd[1]: Starting Disk Manager...
    9月 26 09:17:35 eric-vm-dev udisksd[835]: udisks daemon version 2.7.6 starting
    9月 26 09:17:42 eric-vm-dev udisksd[835]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
    9月 26 09:17:43 eric-vm-dev udisksd[835]: Failed to load the 'mdraid' libblockdev plugin
    9月 26 09:17:45 eric-vm-dev systemd[1]: Started Disk Manager.
    9月 26 09:17:45 eric-vm-dev udisksd[835]: Acquired the name org.freedesktop.UDisks2 on the system message bus

其它Unit

mount.mount

    A unit configuration file whose name ends in ".mount" encodes information about a file system mount point controlled and supervised by systemd.
    Mount units must be named after the mount point directories they control. Example: the mount point /home/lennart must be configured in a unit file home-lennart.mount.
    
    Mount files must include a [Mount] section, which carries information about the file system mount points it supervises. 
        What=
            Takes an absolute path of a device node, file or other resource to mount.
            If this refers to a device node, a dependency on the respective device unit is automatically created.
            This option is mandatory.
        Where=
            Takes an absolute path of a directory for the mount point; in particular, the destination cannot be a symbolic link. 
            If the mount point does not exist at the time of mounting, it is created. 
            This string must be reflected in the unit filename. This option is mandatory.
        Type=
        ......

automount.automount

    A unit configuration file whose name ends in ".automount" encodes information about a file system automount point controlled and supervised by systemd.
    Automount units must be named after the automount directories they control. Example: the automount point /home/lennart must be configured in a unit file home-lennart.automount.
    Note that automount units cannot be templated, nor is it possible to add multiple names to an automount unit by creating additional symlinks to its unit file.
    
    For each automount unit file a matching mount unit file must exist which is activated when the automount path is accessed. 
    Example: if an automount unit home-lennart.automount is active and the user accesses /home/lennart the mount unit home-lennart.mount will be activated.
    
    Automount units may either be configured via unit files, or via /etc/fstab, If an automount point is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence.
    
    Automount files must include an [Automount] section, which carries information about the file system automount points it supervises.
        Where=
            Takes an absolute path of a directory of the automount point. If the automount point does not exist at time that the automount point is installed, it is created. 
            This string must be reflected in the unit filename. This option is mandatory.
        DirectoryMode=
            Directories of automount points (and any parent directories) are automatically created if needed.
        TimeoutIdleSec=

swap.swap

    A unit configuration file whose name ends in ".swap" encodes information about a swap device or file for memory paging controlled and supervised by systemd.
    Swap units must be named after the devices or files they control. Example: the swap device /dev/sda5 must be configured in a unit file dev-sda5.swap.
    Note that swap units cannot be templated, nor is possible to add multiple names to a swap unit by creating additional symlinks to it.
    
    Swap files must include a [Swap] section, which carries information about the swap device it supervises.
        What=
            Takes an absolute path of a device node or file to use for paging.
        Priority=
            Swap priority to use when activating the swap device or file. This takes an integer.
        Options=
        TimeoutSec=