| Server IP : 209.38.156.173 / Your IP : 216.73.216.122 [ Web Server : Apache/2.4.52 (Ubuntu) System : Linux lakekumayuhotel 5.15.0-136-generic #147-Ubuntu SMP Sat Mar 15 15:53:30 UTC 2025 x86_64 User : root ( 0) PHP Version : 8.1.2-1ubuntu2.22 Disable Function : NONE Domains : 2 Domains MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /snap/core20/2599/lib/systemd/system/ |
Upload File : |
# rtc-sys-time-init@.service is enabled either by generator rtc-sys-time-init-generator or # by udev rule in 90-rtc-sys-time-init.rules, depending on kernel command line parameter # ubuntu_core.rtc_sys_time_init=dev/rtc*. When the parameter is provided the generator # instantiates rtc-sys-time-init@dev-rtc*.service by hooking it into sysinit.target with # symlink in /run/systemd/generator*/sysinit.target.wants. Otherwise the udev rule will # instantiate rtc-sys-time-init@dev-rtc*.service if the RTC driver/module set the system # time as indicated by device attribute hctosys==1. # # This service addresses two different scenarios in order: # 1) Ensure system time is not behind the most recent epoch/clock file timestamps. # This addresses: https://github.com/snapcore/core20/pull/136 # 2) Ensure the system time is set to valid RTC time when this is requested with # kernel command line parameter ubuntu_core.rtc_sys_time_init=/dev/rtc* # # This service relies on udev rule from 90-rtc-sys-time-init.rules to create device units # dev-rtc*.device for all available RTC devices. [Unit] Description=Correct system time and sync to RTC time DefaultDependencies=no After=%i.device Requires=%i.device Before=systemd-timesyncd.service Conflicts=shutdown.target Before=shutdown.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/usr/lib/core/rtc-sys-time-init /%I