fedora-docs-l10n/fedora-system-administrat/f29/pages/servers/Configuring_NTP_Using_the_chrony_Suite

Zen

	English	Korean	Actions
	`ntpd` includes drivers for many reference clocks whereas `chronyd` relies on other programs, for example [application]gpsd, to access the data from the reference clocks.
	Choosing Between NTP Daemons	NTP 데몬 사이에서 선택하기
	[application]Chrony should be considered for all systems which are frequently suspended or otherwise intermittently disconnected and reconnected to a network. Mobile and virtual systems for example.
	The `NTP` daemon (`ntpd`) should be considered for systems which are normally kept permanently on. Systems which are required to use broadcast or multicast `IP`, or to perform authentication of packets with the `Autokey` protocol, should consider using `ntpd`. [application]Chrony only supports symmetric key authentication using a message authentication code (MAC) with MD5, SHA1 or stronger hash functions, whereas `ntpd` also supports the `Autokey` authentication protocol which can make use of the PKI system. `Autokey` is described in [citetitle]_RFC 5906_.
	Understanding chrony and Its Configuration	chrony와 이 구성 이해하기
	Understanding chronyd	chronyd 이해하기
	The [application]chrony daemon, `chronyd`, running in user space, makes adjustments to the system clock which is running in the kernel. It does this by consulting external time sources, using the `NTP` protocol, when ever network access allows it to do so. When external references are not available, `chronyd` will use the last calculated drift stored in the drift file. It can also be commanded manually to make corrections, by [application]chronyc.
	Understanding chronyc	chronyc 이해하기
	The [application]chrony daemon, `chronyd`, can be controlled by the command line utility [application]chronyc. This utility provides a command prompt which allows entering of a number of commands to make changes to `chronyd`. The default configuration is for `chronyd` to only accept commands from a local instance of [application]chronyc, but [application]chronyc can be used to alter the configuration so that `chronyd` will allow external control. [application]chronyc can be run remotely after first configuring `chronyd` to accept remote connections. The `IP` addresses allowed to connect to `chronyd` should be tightly controlled.
	Understanding the chrony Configuration Commands	chrony 구성 명령을 이해하기
	The default configuration file for `chronyd` is `/etc/chrony.conf`. The [option]`-f` option can be used to specify an alternate configuration file path. See the `chronyd` man page for further options. For a complete list of the directives that can be used see [citetitle]_link:++https://chrony.tuxfamily.org/manual.html#Configuration-file++[https://chrony.tuxfamily.org/manual.html#Configuration-file]_. Below is a selection of configuration options:
	Comments	주석
	Comments should be preceded by #, %, ; or !	주석 앞에는 y #, %, ; 또는 !
	allow	허용
	Optionally specify a host, subnet, or network from which to allow `NTP` connections to a machine acting as `NTP` server. The default is not to allow connections. Examples:
	[subs="quotes"]	[subs="quotes"]
	allow server1.example.com	allow server1.example.com
	Use this form to specify a particular host, by its host name, to be allowed access.	이와 같은 형식을 사용하여 접근이 허용된 호스트 이름으로 특정 호스트를 지정합니다.
	allow 192.0.2.0/24	allow 192.0.2.0/24
	Use this form to specify a particular network to be allowed access.	이와 같은 형식을 사용하여 접근을 허용 할 특정한 네트워크를 지정합니다.
	allow 2001:db8::/32	allow 2001:db8::/32
	Use this form to specify an `IPv6` address to be allowed access.	이와 같은 형식을 사용하여 접근을 허용 할 `IPv6` 주소를 지정합니다.
	cmdallow	cmdallow
	This is similar to the [command]#allow# directive (see section [command]#allow#), except that it allows control access (rather than `NTP` client access) to a particular subnet or host. (By "control access" is meant that [application]chronyc can be run on those hosts and successfully connect to `chronyd` on this computer.) The syntax is identical. There is also a [command]#cmddeny all# directive with similar behavior to the [command]#cmdallow all# directive.
	dumpdir	덤프디렉토리
	Path to the directory to save the measurement history across restarts of `chronyd` (assuming no changes are made to the system clock behavior whilst it is not running). If this capability is to be used (via the [command]#dumponexit# command in the configuration file, or the [command]#dump# command in [application]chronyc), the [command]#dumpdir# command should be used to define the directory where the measurement histories are saved.
	dumponexit	dumponexit
	If this command is present, it indicates that `chronyd` should save the measurement history for each of its time sources recorded whenever the program exits. (See the [command]#dumpdir# command above).
	local	로컬
	The [command]#local# keyword is used to allow `chronyd` to appear synchronized to real time from the viewpoint of clients polling it, even if it has no current synchronization source. This option is normally used on the "master" computer in an isolated network, where several computers are required to synchronize to one another, and the "master" is kept in line with real time by manual input.
	An example of the command is:	명령의 예는 다음과 같습니다:

Loading…

simmon

Translation changed

English

Korean 0 characters edited Current translation Translated

a year ago

simmon

Contributor joined

Contributor joined a year ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Korean
No related strings found in the glossary.

String information

Source string description

type: Plain text

Source string location

pages/servers/Configuring_NTP_Using_the_chrony_Suite.adoc:78 • pages/servers/Configuring_NTP_Using_the_chrony_Suite.adoc:85 • pages/servers/Configuring_NTP_Using_the_chrony_Suite.adoc:92

String age

2 years ago

Last updated

10 months ago

Source string age

4 years ago

Translation file

po/ko/f29/pages/servers/Configuring_NTP_Using_the_chrony_Suite.po, string 35