The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.
Zen

Translation

English type: delimited block -
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
63/630 · 63

This translation is currently locked.

English Korean Actions
Understanding the Drift File
드리프트 파일 이해하기
The drift file is used to store the frequency offset between the system clock running at its nominal frequency and the frequency required to remain in synchronization with UTC. If present, the value contained in the drift file is read at system start and used to correct the clock source. Use of the drift file reduces the time required to achieve a stable and accurate time. The value is calculated, and the drift file replaced, once per hour by `ntpd`. The drift file is replaced, rather than just updated, and for this reason the drift file must be in a directory for which the `ntpd` has write permissions.
 
UTC, Timezones, and DST
UTC, 시간대, 그리고 DST
As `NTP` is entirely in UTC (Universal Time, Coordinated), Timezones and DST (Daylight Saving Time) are applied locally by the system. The file `/etc/localtime` is a copy of, or symlink to, a zone information file from `/usr/share/zoneinfo`. The RTC may be in localtime or in UTC, as specified by the 3rd line of `/etc/adjtime`, which will be one of LOCAL or UTC to indicate how the RTC clock has been set. Users can easily change this setting using the checkbox `System Clock Uses UTC` in the [application]*Date and Time* graphical configuration tool. See xref:basic-system-configuration/Configuring_the_Date_and_Time.adoc#ch-Configuring_the_Date_and_Time[Configuring the Date and Time] for information on how to use that tool. Running the RTC in UTC is recommended to avoid various problems when daylight saving time is changed.
 
The operation of `ntpd` is explained in more detail in the man page `ntpd(8)`. The resources section lists useful sources of information. See xref:Configuring_NTP_Using_ntpd.adoc#s1-ntpd_additional-resources[Additional Resources].
 
Authentication Options for NTP
NTP를 위한 인증 옵션
`NTPv4` added support for the Autokey Security Architecture, which is based on public asymmetric cryptography while retaining support for symmetric key cryptography. The Autokey Security Architecture is described in [citetitle]_link:++https://www.rfc-editor.org/info/rfc5906++[RFC 5906 Network Time Protocol Version 4: Autokey Specification]_. The man page `ntp_auth(5)` describes the authentication options and commands for `ntpd`.
 
An attacker on the network can attempt to disrupt a service by sending `NTP` packets with incorrect time information. On systems using the public pool of `NTP` servers, this risk is mitigated by having more than three `NTP` servers in the list of public `NTP` servers in `/etc/ntp.conf`. If only one time source is compromised or spoofed, `ntpd` will ignore that source. You should conduct a risk assessment and consider the impact of incorrect time on your applications and organization. If you have internal time sources you should consider steps to protect the network over which the `NTP` packets are distributed. If you conduct a risk assessment and conclude that the risk is acceptable, and the impact to your applications minimal, then you can choose not to use authentication.
 
The broadcast and multicast modes require authentication by default. If you have decided to trust the network then you can disable authentication by using [command]#disable auth# directive in the `ntp.conf` file. Alternatively, authentication needs to be configured by using SHA1 or MD5 symmetric keys, or by public (asymmetric) key cryptography using the Autokey scheme. The Autokey scheme for asymmetric cryptography is explained in the `ntp_auth(8)` man page and the generation of keys is explained in `ntp-keygen(8`). To implement symmetric key cryptography, see xref:Configuring_NTP_Using_ntpd.adoc#s2_Configuring_Symmetric_Authentication_Using_a_Key[Configuring Symmetric Authentication Using a Key] for an explanation of the [option]`key` option.
 
Managing the Time on Virtual Machines
가상 장비에서 시간을 관리하기
Virtual machines cannot access a real hardware clock and a virtual clock is not stable enough as the stability is dependent on the host systems work load. For this reason, para-virtualized clocks should be provided by the virtualization application in use (for more information see _https://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administration_Guide/sect-Virtualization-Tips_and_tricks-Libvirt_Managed_Timers.html[Libvirt Managed Timers]_ in the _Virtualization Administration Guide_). On {MAJOROS} with [application]*KVM* the default clock source is [option]`kvm-clock`. See the [citetitle]_link:++https://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/chap-Virtualization-KVM_guest_timing_management.html++[KVM guest timing management]_ chapter of the [citetitle]_Virtualization Host Configuration and Guest Installation Guide_.
 
Understanding Leap Seconds
도약 시간 이해하기
Greenwich Mean Time (GMT) was derived by measuring the solar day, which is dependent on the Earth's rotation. When atomic clocks were first made, the potential for more accurate definitions of time became possible. In 1958, International Atomic Time (TAI) was introduced based on the more accurate and very stable atomic clocks. A more accurate astronomical time, Universal Time 1 (UT1), was also introduced to replace GMT. The atomic clocks are in fact far more stable than the rotation of the Earth and so the two times began to drift apart. For this reason UTC was introduced as a practical measure. It is kept within one second of UT1 but to avoid making many small trivial adjustments it was decided to introduce the concept of a _leap second_ in order to reconcile the difference in a manageable way. The difference between UT1 and UTC is monitored until they drift apart by more than half a second. Then only is it deemed necessary to introduce a one second adjustment, forward or backward. Due to the erratic nature of the Earth's rotational speed, the need for an adjustment cannot be predicted far into the future. The decision as to when to make an adjustment is made by the [citetitle]_link:++https://www.iers.org++[International Earth Rotation and Reference Systems Service (IERS)]_. However, these announcements are important only to administrators of Stratum 1 servers because `NTP` transmits information about pending leap seconds and applies them automatically.
 
Understanding the ntpd Configuration File
ntpd 구성 파일 이해하기
The daemon, `ntpd`, reads the configuration file at system start or when the service is restarted. The default location for the file is `/etc/ntp.conf` and you can view the file by entering the following command:
 
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
The configuration commands are explained briefly later in this chapter, see xref:Configuring_NTP_Using_ntpd.adoc#s1-Configure_NTP[Configure NTP], and more verbosely in the `ntp.conf(5)` man page.
구성 명령은 이 장의 설명서 부분에서 더 자세하게 설명되고, xref:Configuring_NTP_Using_ntpd.adoc#s1-Configure_NTP[Configure NTP]를 참고하고, `ntp.conf(5)`man 설명서에서 더 자세하게 설명합니다.
Here follows a brief explanation of the contents of the default configuration file:
다음은 기본 구성 파일의 내용에 대한 간략한 설명입니다:
The driftfile entry
드리프트파일 항목
A path to the drift file is specified, the default entry on {MAJOROS} is:
드리프트 파일에 경로가 지정되고, {MAJORS}에서 기본 항목은 다음과 같습니다:
driftfile /var/lib/ntp/drift
driftfile /var/lib/ntp/drift
If you change this be certain that the directory is writable by `ntpd`. The file contains one value used to adjust the system clock frequency after every system or service start. See xref:Configuring_NTP_Using_ntpd.adoc#s1-Understanding_the_Drift_File[Understanding the Drift File] for more information.
 
The access control entries
접근 제어 항목
The following line sets the default access control restriction:
다음 줄은 기본 접근 제어 제한을 설정합니다:
restrict default nomodify notrap nopeer noquery
제한 기본 nomodify notrap nopeer noquery
The [option]`nomodify` options prevents any changes to the configuration.
[option]`nomodify`선택은 구성에서 변경하는 것을 예방합니다.
The [option]`notrap` option prevents `ntpdc` control message protocol traps.
[option]`notrap` 선택은`ntpdc` 제어 메시지 통신규약 트랩을 방지합니다.
The [option]`nopeer` option prevents a peer association being formed.
[option]`nopeer` 선택은 같은 부류로 협력 되어지는 형태를 예방합니다.
The [option]`noquery` option prevents `ntpq` and `ntpdc` queries, but not time queries, from being answered.
 
The `ntpq` and `ntpdc` queries can be used in amplification attacks, therefore do not remove the [option]`noquery` option from the [command]#restrict default# command on publicly accessible systems.
 
See [citetitle]_link:++https://access.redhat.com/security/cve/CVE-2013-5211++[CVE-2013-5211]_ for more details.
더 자세히 알기 위해 [citetitle]_link:++https://access.redhat.com/security/cve/CVE-2013-5211++[CVE-2013-5211]_를 참고하세요.

Loading…

User avatar simmon

Translation added
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
2 years ago
User avatar None

String updated in the repository
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
2 years ago
User avatar simmon

Translation added
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
2 years ago
User avatar None

String updated in the repository
~]${nbsp}pass:attributes[{blank}][command]#less /etc/ntp.conf#
 
2 years ago
Browse all string changes

Things to check

Unchanged translation 1

Source and translation are identical

Reset

Glossary

English Korean
No related strings found in the glossary.

12138373 String information

Source string description
type: delimited block -
Flags
no-wrap
Source string location
./pages/servers/Configuring_NTP_Using_ntpd.adoc:104
String age
2 years ago
Last updated
a year ago
Source string age
2 years ago
Translation file
po/ko/f34/pages/servers/Configuring_NTP_Using_ntpd.po, string 49