uyuni/docs client-configuration-manager-4.3-MU-4.3.13 — Chinese (China) (zh_CN) @ openSUSE Weblate: Push via SSH and Push via Salt SSH are used …

Translation

English type: Plain text

Chinese (China) (zh_CN)

Needs editing

Only reviewers can change approved strings, please add a suggestion if you think the string should be changed.

Skip

	English	Chinese (China) (zh_CN)	Actions
	For example, you may have a file applicable to all of your servers that differs only in IP address and host name. Rather than manage a separate configuration file for each server, you can create a single file, such as [path]``server.conf``, with the IP address and host name macros included.	例如，您可能有一个适用于所有服务器，但只有 IP 地址和主机名不同的文件。您无需为每台服务器都管理一个单独的配置文件，而是可以创建一个文件（例如 [path]``server.conf``），在其中包含 IP 地址和主机名宏。
	hostname={\| rhn.system.hostname \|} ip_address={\| rhn.system.net_interface.ip_address(eth0) \|}	hostname={\| rhn.system.hostname \|} ip_address={\| rhn.system.net_interface.ip_address(eth0) \|}
	When the file is delivered to individual systems, whether through a scheduled action in the {productname} {webui} or at the command line with the {productname} Configuration Client ([command]``mgrcfg-client``), the variables will be replaced with the host name and IP address of the system as recorded in {productname}'s system profile. In this example, the deployed version will look similar to this:	当文件传送到各个系统时（无论是通过 {productname} {webui} 中安排的操作，还是在命令行中使用 {productname} 配置客户端 ([command]``mgrcfg-client``) 传送），变量将被替换为 {productname} 的系统配置文件中所记录的系统主机名和 IP 地址。在此示例中，部署的版本将如下所示：
	hostname=test.example.domain.com ip_address=177.18.54.7	hostname=test.example.domain.com ip_address=177.18.54.7
	To capture custom system information, insert the key label into the custom information macro (``rhn.system.custom_info``). For example, if you developed a key labeled "asset" you can add it to the custom information macro in a configuration file to have the value substituted on any system containing it. The macro would look like this:	要获取自定义系统信息，请在自定义信息宏 (``rhn.system.custom_info``) 中插入键标签。例如，如果您开发了一个标记为“asset”的键，则可以在配置文件中将其添加到自定义信息宏中，以便在任何包含该键的系统上替换该值。该宏将如下所示：
	asset={@ rhn.system.custom_info(asset) @}	asset={@ rhn.system.custom_info(asset) @}
	When the file is deployed to a system containing a value for that key, the macro gets translated, resulting in a string similar to this:	将文件部署到包含该键值的系统上时，宏将会被转译，生成如下所示的字符串：
	asset=Example#456	asset=Example#456
	To include a default value (for example, if one is required to prevent errors), you can append it to the custom information macro, like this:	如果要包含默认值（例如，如果需要默认值以防发生错误），您可以将其追加到自定义信息宏中，如下所示：
	asset={@ rhn.system.custom_info(asset) = 'Asset #' @}	asset={@ rhn.system.custom_info(asset) = 'Asset #' @}
	This default is overridden by the value on any system containing it.	此默认值会被任何包含该值的系统上的值覆盖。
	The {productname} Configuration Manager ([command]``mgrcfg-manager``) is available on {productname} client machines to assist with system management. It will not translate or alter files, as the tool is system agnostic. The [command]``mgrcfg-manager`` command does not depend on system settings. Binary files cannot be interpolated.	在 {productname} 客户端计算机上可以使用 {productname} 配置管理器 ([command]``mgrcfg-manager``) 来协助进行系统管理。它不会转译或更改文件，因为该工具与系统没有关联。[command]``mgrcfg-manager`` 命令不依赖于系统设置。无法插入二进制文件。
	Client Management Methods	客户端管理方法
	There are a number of ways that the {productname} Server can communicate with clients. Which one you use depends on the type of client, and your network architecture.	{productname} 服务器可以使用多种方法与客户端进行通讯。您使用的方法取决于客户端类型以及网络体系结构。
	The {productname} daemon ([command]``rhnsd``) runs on traditional client systems and periodically connects with {productname} to check for new updates and notifications. It does not apply to Salt clients.	{productname} 守护程序 ([command]``rhnsd``) 在传统客户端系统上运行，会定期与 {productname} 连接以检查有无新更新和通知。它不适用于 Salt 客户端。
	Push via SSH and Push via Salt SSH are used in environments where clients cannot reach the {productname} Server directly. In this environment, clients are located in a firewall-protected zone called a DMZ. No system within the DMZ is authorized to open a connection to the internal network, including the {productname} Server.	在客户端无法直接访问 {productname} 服务器的环境中，将会采用通过 SSH 推送和通过 Salt SSH 推送的方法。在此环境中，客户端位于受防火墙保护的区域，该区域称为 DMZ。DMZ 内的所有系统均无权打开连至内部网络（包括 {productname} 服务器）的连接。
	OSAD is an alternative contact method between {productname} and traditional clients. OSAD allows traditional clients to execute scheduled actions immediately. It does not apply to Salt clients.	OSAD 是 {productname} 与传统客户端之间的一种替代联系方法。OSAD 允许传统客户端立即执行安排的操作。它不适用于 Salt 客户端。
	Migrate Traditional Clients to {salt} Clients	将传统客户端迁移为 {salt} 客户端
	To migrate a system from a traditional to a {salt} client, the user can create a {salt} bootstrap script and re-register the client system with it.	要将传统系统迁移为 {salt} 客户端，用户可以创建一个 {salt} 引导脚本，并使用该脚本重新注册客户端系统。
	This could be done by:	此操作可以通过以下步骤完成：
	generating a reactivation key for the client,	为客户端生成重新激活密钥
	creating a bootstrap script with a specific activation key, and	创建包含特定激活密钥的引导脚本
	running the bootstrap script to register the client, with the aforementioned reactivation key.	运行引导脚本以使用上面所述的重新激活密钥注册客户端
	Generate Reactivation Key	生成重新激活密钥
	A reactivation key can be used to re-register the client and regain all {productname} settings. For more information on how to create reactivation key, see xref:client-configuration:activation-keys.adoc#reactivation_keys[].	重新激活密钥可用于重新注册客户端和重新获取所有 {productname} 设置。有关如何创建重新激活密钥的详细信息，请参见 xref:client-configuration:activation-keys.adoc#reactivation_keys[]。
	Create Bootstrap Script	创建引导脚本
	A bootstrap script can be created with the {webui} or from the command line. For more information about creating bootstrap script, see xref:client-configuration:registration-bootstrap.adoc[], and for generating a suitable activation key in advance, see xref:client-configuration:activation-keys.adoc[].	您可以使用 {webui} 或从命令行中创建引导脚本。有关如何创建引导脚本的详细信息，请参见 xref:client-configuration:registration-bootstrap.adoc[]，有关如何提前生成适当的激活密钥的信息，请参见 xref:client-configuration:activation-keys.adoc[]。
	Use the activation key you generating in advance when creating the bootstrap script.	在创建引导脚本时，使用您提前生成的激活密钥。
	When the bootstrap script is generated, it is stored on the server in the [path]``/srv/www/htdocs/pub/bootstrap`` directory. Alternatively, you can access the bootstrap script over HTTPS. Replace [literal]``<example.com>`` with the host name of the {productname} Server:	系统生成引导脚本后，会将其存储在服务器的 [path]``/srv/www/htdocs/pub/bootstrap`` 目录中。或者，您也可以通过 HTTPS 访问引导脚本。请将 [literal]``<example.com>`` 替换为 {productname} 服务器的主机名：
	https://<example.com>/pub/bootstrap/bootstrap.sh	https://<example.com>/pub/bootstrap/bootstrap.sh
	Bootstrap script will try to install [package]``venv-salt-minion`` for {salt} clients if it is available in the bootstrap repository, or [package]``salt-minion`` if there is no {salt} bundle in the bootstrap repository. It is possible to avoid installing {salt} bundle and keep using [package]``salt-minion`` if you need it.	如果引导储存库中提供了 [package]``venv-salt-minion``，引导脚本将尝试为 {salt} 客户端安装该软件包，如果引导储存库中没有 {salt} 捆绑包，则会安装 [package]``salt-minion``。如果您需要 [package]``salt-minion``，则可以避免安装 {salt} 捆绑包，继续使用前者。

Loading…

graceyu

Translation approved

English

Chinese (China) (zh_CN) 0 characters edited Current translation Approved

2 weeks ago

None

String added in the repository

English

Chinese (China) (zh_CN) 143 characters edited Current translation Translated

3 weeks ago

Browse all string changes

Things to check

Consecutive duplicated words

Text contains the same word twice in a row: DMZ

Reset

Glossary

English	Chinese (China) (zh_CN)
No related strings found in the glossary.

String information

Source string description

type: Plain text

Source string location

modules/client-configuration/pages/contact-methods-intro.adoc:4

String age

3 weeks ago

Last updated

2 weeks ago

Source string age

3 weeks ago

Translation file

l10n-weblate/client-configuration/zh_CN.po, string 1505