One Hat Cyber Team

Your IP: 216.73.216.231
Server IP: 13.127.59.50
Server: Linux ip-172-31-46-210 5.15.0-1033-aws #37~20.04.1-Ubuntu SMP Fri Mar 17 11:39:30 UTC 2023 x86_64
Server Software: Apache/2.4.41 (Ubuntu)
PHP Version: 7.4.3-4ubuntu2.29
Buat File | Buat Folder

Dir : ~/snap/core22/current/lib/systemd/system/

Edit File: rtc-sys-time-init@.service

# 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