Author: keichwa
Date: 2014-10-07 17:49:12 +0200 (Tue, 07 Oct 2014)
New Revision: 89784
Modified:
trunk/yast/zh_CN/po/add-on-creator.zh_CN.po
trunk/yast/zh_CN/po/add-on.zh_CN.po
trunk/yast/zh_CN/po/audit-laf.zh_CN.po
trunk/yast/zh_CN/po/auth-client.zh_CN.po
trunk/yast/zh_CN/po/auth-server.zh_CN.po
trunk/yast/zh_CN/po/autoinst.zh_CN.po
trunk/yast/zh_CN/po/base.zh_CN.po
trunk/yast/zh_CN/po/bootloader.zh_CN.po
trunk/yast/zh_CN/po/ca-management.zh_CN.po
trunk/yast/zh_CN/po/cio.zh_CN.po
trunk/yast/zh_CN/po/cluster.zh_CN.po
trunk/yast/zh_CN/po/control-center.zh_CN.po
trunk/yast/zh_CN/po/control.zh_CN.po
trunk/yast/zh_CN/po/country.zh_CN.po
trunk/yast/zh_CN/po/crowbar.zh_CN.po
trunk/yast/zh_CN/po/dhcp-server.zh_CN.po
trunk/yast/zh_CN/po/dns-server.zh_CN.po
trunk/yast/zh_CN/po/drbd.zh_CN.po
trunk/yast/zh_CN/po/fcoe-client.zh_CN.po
trunk/yast/zh_CN/po/firewall-services.zh_CN.po
trunk/yast/zh_CN/po/firewall.zh_CN.po
trunk/yast/zh_CN/po/firstboot.zh_CN.po
trunk/yast/zh_CN/po/ftp-server.zh_CN.po
trunk/yast/zh_CN/po/gtk.zh_CN.po
trunk/yast/zh_CN/po/http-server.zh_CN.po
trunk/yast/zh_CN/po/inetd.zh_CN.po
trunk/yast/zh_CN/po/installation.zh_CN.po
trunk/yast/zh_CN/po/instserver.zh_CN.po
trunk/yast/zh_CN/po/iplb.zh_CN.po
trunk/yast/zh_CN/po/iscsi-client.zh_CN.po
trunk/yast/zh_CN/po/iscsi-lio-server.zh_CN.po
trunk/yast/zh_CN/po/iscsi-server.zh_CN.po
trunk/yast/zh_CN/po/isns.zh_CN.po
trunk/yast/zh_CN/po/kdump.zh_CN.po
trunk/yast/zh_CN/po/kerberos-server.zh_CN.po
trunk/yast/zh_CN/po/kerberos.zh_CN.po
trunk/yast/zh_CN/po/languages_db.zh_CN.po
trunk/yast/zh_CN/po/ldap-client.zh_CN.po
trunk/yast/zh_CN/po/ldap-server.zh_CN.po
trunk/yast/zh_CN/po/ldap.zh_CN.po
trunk/yast/zh_CN/po/linux-user-mgmt.zh_CN.po
trunk/yast/zh_CN/po/live-installer.zh_CN.po
trunk/yast/zh_CN/po/lxc.zh_CN.po
trunk/yast/zh_CN/po/mail.zh_CN.po
trunk/yast/zh_CN/po/multipath.zh_CN.po
trunk/yast/zh_CN/po/ncurses-pkg.zh_CN.po
trunk/yast/zh_CN/po/ncurses.zh_CN.po
trunk/yast/zh_CN/po/network.zh_CN.po
trunk/yast/zh_CN/po/nfs.zh_CN.po
trunk/yast/zh_CN/po/nfs_server.zh_CN.po
trunk/yast/zh_CN/po/nis.zh_CN.po
trunk/yast/zh_CN/po/nis_server.zh_CN.po
trunk/yast/zh_CN/po/ntp-client.zh_CN.po
trunk/yast/zh_CN/po/oneclickinstall.zh_CN.po
trunk/yast/zh_CN/po/online-update-configuration.zh_CN.po
trunk/yast/zh_CN/po/online-update.zh_CN.po
trunk/yast/zh_CN/po/opensuse_mirror.zh_CN.po
trunk/yast/zh_CN/po/packager.zh_CN.po
trunk/yast/zh_CN/po/pam.zh_CN.po
trunk/yast/zh_CN/po/pkg-bindings.zh_CN.po
trunk/yast/zh_CN/po/printer.zh_CN.po
trunk/yast/zh_CN/po/product-creator.zh_CN.po
trunk/yast/zh_CN/po/proxy.zh_CN.po
trunk/yast/zh_CN/po/qt-pkg.zh_CN.po
trunk/yast/zh_CN/po/qt.zh_CN.po
trunk/yast/zh_CN/po/rdp.zh_CN.po
trunk/yast/zh_CN/po/rear.zh_CN.po
trunk/yast/zh_CN/po/registration.zh_CN.po
trunk/yast/zh_CN/po/reipl.zh_CN.po
trunk/yast/zh_CN/po/relocation-server.zh_CN.po
trunk/yast/zh_CN/po/s390.zh_CN.po
trunk/yast/zh_CN/po/samba-client.zh_CN.po
trunk/yast/zh_CN/po/samba-server.zh_CN.po
trunk/yast/zh_CN/po/samba-users.zh_CN.po
trunk/yast/zh_CN/po/scanner.zh_CN.po
trunk/yast/zh_CN/po/security.zh_CN.po
trunk/yast/zh_CN/po/services-manager.zh_CN.po
trunk/yast/zh_CN/po/slp-server.zh_CN.po
trunk/yast/zh_CN/po/snapper.zh_CN.po
trunk/yast/zh_CN/po/sound.zh_CN.po
trunk/yast/zh_CN/po/squid.zh_CN.po
trunk/yast/zh_CN/po/sshd.zh_CN.po
trunk/yast/zh_CN/po/storage.zh_CN.po
trunk/yast/zh_CN/po/sudo.zh_CN.po
trunk/yast/zh_CN/po/support.zh_CN.po
trunk/yast/zh_CN/po/sysconfig.zh_CN.po
trunk/yast/zh_CN/po/tftp-server.zh_CN.po
trunk/yast/zh_CN/po/timezone_db.zh_CN.po
trunk/yast/zh_CN/po/tune.zh_CN.po
trunk/yast/zh_CN/po/update.zh_CN.po
trunk/yast/zh_CN/po/users.zh_CN.po
trunk/yast/zh_CN/po/vm.zh_CN.po
trunk/yast/zh_CN/po/wagon.zh_CN.po
trunk/yast/zh_CN/po/wol.zh_CN.po
trunk/yast/zh_CN/po/xpram.zh_CN.po
trunk/yast/zh_CN/po/yast2-apparmor.zh_CN.po
Log:
merged
Modified: trunk/yast/zh_CN/po/add-on-creator.zh_CN.po
===================================================================
--- trunk/yast/zh_CN/po/add-on-creator.zh_CN.po 2014-10-07 15:48:22 UTC (rev 89783)
+++ trunk/yast/zh_CN/po/add-on-creator.zh_CN.po 2014-10-07 15:49:12 UTC (rev 89784)
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: add-on-creator\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-24 10:55+0100\n"
+"POT-Creation-Date: 2014-07-04 15:51+0200\n"
"PO-Revision-Date: 2013-10-31 02:08+0800\n"
"Last-Translator: 玛格丽特 · 苏 Process ID number is a number that uniquely identifies one specific process or running program (this number is valid only during the lifetime of that process).<br><br> <b>Severity Level:</b> Select the lowest severity level for security events that you would like to be included in the report. The selected severity level, and above, will be included in the reports.<br><br> <b>Detail:</b> A source to which the profile has denied access. This includes capabilities and files. You can use this field to report the resources are not allowed to be accessed by profiles.<br><br> <b>Mode:</b> The Mode is the permission that the profile grants to the program or process to which it is applied. The options are: r (read) w (write) l (link) x (execute)<br><br> <b>Access Type:</b> The access type describes what is actually happening with the security event. The options are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> Enables you to export a CSV (comma separated values) or ht
ml file. The CSV file separates pieces of data in the log entries with commas using a standard data format for importing into table-oriented applications. You can enter a pathname for your exported report by typing in the full pathname in the field provided.</p>"
+#~ msgstr "“报告配置”对话框使您能够过滤在以前屏幕中选择的存档报告。要按<b>日期范围</b>过滤:<br><br><ol> <li>请单击<b>按日期范围过滤</b>。该字段变为活动状态。<li>输入描述报告范围的开始和结束日期。<li>输入其他过滤参数。参考以下的参数定义。</ol>以下定义有助于您在“报告配置”对话框中输入过滤参数:<br><br> <b>程序名称模式:</b> 当您输入的程序名称或模式与所涉及程序的二进制可执行文件的名称相匹配时,报告将显示针对特定程序发生的安全性事件。<br><br> <b>设置存档名称模式:</b>当您输入设置存档名称时,报告将显示针对指定设置存档生成的安全性事件。由此您可以看到特定设置存档所限制的内容。<br><br><b>PID 号:</b> 进程 ID 号是一个编号,用来唯一标识某个特定进程或正在运行的程序(此编号仅在该进程的有效期内有效)。
<br><br> <b>严重性级别:</b>请为您要在报告中包含的安全性事件选择最低的严重性级别。选定的严重性级别及更高级别将包含在报告中。<br><br><b>细节:</b>设置存档已拒绝访问的源。这包含功能和文件。您可以使用此字段来报告不允许设置存档访问的资源。<br><br><b>方式:</b>“方式”是设置存档授予应用该设置存档的程序或进程的许可权限。其选项为:r(读)w(写)l(链接)x(执行)<br><br> <b>访问类型:</b>访问类型描述了安全性事件真正发生的内容。其选项为:允许、拒绝或审计。<br><br><b>CSV 或 HTML:</b>使您能够导出 CSV(逗号分隔值)或 html 文件。CSV 文件使用标准数据格式,将日志条目中的数据片段用逗号分隔开,以便于导入面向表的应用程序。您可以输入已导出报告的路径名,方法是在提供的字段中输入它的完整路径名。" #, fuzzy
-#~ msgid ""
-#~ "<p>The AppArmor On-Demand Report screen displays an instantly generated "
-#~ "version of one of the following reports. <b>Executive Security Summary:"
-#~ "b> A combined report, consisting of one or more Security incident reports "
-#~ "from one or more machines. This report provides a single view of "
-#~ "security events on multiple machines.<br><br> <b>Applications Audit "
-#~ "Report:</b> An auditing tool that reports which application servers are "
-#~ "running and whether the applications are confined by AppArmor. "
-#~ "Application servers are applications that accept incoming network "
-#~ "connections. <br><br> <b>Security Incident Report:</b> A report that "
-#~ "displays application security for a single host. It reports policy "
-#~ "violations for locally confined applications during a specific time "
-#~ "period. You can edit and customize this report, or add new versions.</p>"
-#~ msgstr ""
-#~ "\"AppArmor 随选报告\"屏幕显示了下列一种报告的随即生成的版本。 <b>执行安全"
-#~ "性摘要:</b>一份合成的报告,由来自一台或多台计算机的一份或多份安全性事件报"
-#~ "告组成。 此报告使您能在单个视图中查看多台计算机上的安全性事件。<br><br> "
-#~ "<b>应用程序审计报告:</b>一种审计工具,可以报告正在运行的应用程序服务器及"
-#~ "这些应用程序是否受 AppArmor 限制。应用程序服务器是一组应用程序,它们接受进"
-#~ "来的网络连接。<br><br> <b>安全性事件报告:</b>一份显示单个主机的应用程序安"
-#~ "全性的报告。 报告特定时间段内本地限制的应用程序的策略违例。您可以编辑并自"
-#~ "定义该报告,或添加新的版本。"
+#~ msgid "<p>The AppArmor On-Demand Report screen displays an instantly generated version of one of the following reports. <b>Executive Security Summary:</b> A combined report, consisting of one or more Security incident reports from one or more machines. This report provides a single view of security events on multiple machines.<br><br> <b>Applications Audit Report:</b> An auditing tool that reports which application servers are running and whether the applications are confined by AppArmor. Application servers are applications that accept incoming network connections. <br><br> <b>Security Incident Report:</b> A report that displays application security for a single host. It reports policy violations for locally confined applications during a specific time period. You can edit and customize this report, or add new versions.</p>"
+#~ msgstr "\"AppArmor 随选报告\"屏幕显示了下列一种报告的随即生成的版本。 <b>执行安全性摘要:</b>一份合成的报告,由来自一台或多台计算机的一份或多份安全性事件报告组成。 此报告使您能在单个视图中查看多台计算机上的安全性事件。<br><br> <b>应用程序审计报告:</b>一种审计工具,可以报告正在运行的应用程序服务器及这些应用程序是否受 AppArmor 限制。应用程序服务器是一组应用程序,它们接受进来的网络连接。<br><br> <b>安全性事件报告:</b>一份显示单个主机的应用程序安全性的报告。 报告特定时间段内本地限制的应用程序的策略违例。您可以编辑并自定义该报告,或添加新的版本。"
#, fuzzy
-#~ msgid ""
-#~ "<p>The Report Configuration dialog enables you to filter the report "
-#~ "selected in the previous screen. To filter by <b>Date Range:</b><br><br> "
-#~ "<ol> <li>Click <b>Filter By Date Range</b>. The fields become active. "
-#~ "<li>Enter the start and end dates that delineate the scope of the "
-#~ "report. <li>Enter other filtering parameters. See below for definitions "
-#~ "of parameters. </ol> The following definitions help you to enter the "
-#~ "filtering parameters in the Report Configuration Dialog: <b>Program Name "
-#~ "Pattern:</b> When you enter a program name or pattern that matches the "
-#~ "name of the executable process of interest, the report will display "
-#~ "security events that have occurred for a specific program.<br><br> "
-#~ "<b>Profile Name Pattern:</b> When you enter the name of the security "
-#~ "profile that is applied to the process, the report will display the "
-#~ "security events that are generated for the specified profile. You can use "
-#~ "this to see what is being confined by a specific profile.<br><br> <b>PID "
-#~ "Number:</b> Process ID number is a number that uniquely identifies one "
-#~ "specific process or running program (this number is valid only during the "
-#~ "lifetime of that process).<br><br> <b>Severity Level:</b> Select the "
-#~ "lowest severity level for security events that you would like to be "
-#~ "included in the report. The selected severity level, and above, will be "
-#~ "included in the reports.<br><br> <b>Detail:</b> A source to which the "
-#~ "profile has denied access. This includes capabilities and files. You can "
-#~ "use this field to report the resources are not allowed to be accessed by "
-#~ "profiles.<br><br> <b>Mode:</b> The Mode is the permission that the "
-#~ "profile grants to the program or process to which it is applied. The "
-#~ "options are: r (read) w (write) l (link) x (execute)<br><br> <b>Access "
-#~ "Type:</b> The access type describes what is actually happening with the "
-#~ "security event. The options are: PERMITTING, REJECTING, or AUDITING."
-#~ "<br><br> <b>CSV or HTML:</b> Enables you to export a CSV (comma separated "
-#~ "values) or HTML file. The CSV file separates pieces of data in the log "
-#~ "entries with commas using a standard data format for importing into table-"
-#~ "oriented applications. You can enter a pathname for your exported report "
-#~ "by typing in the full pathname in the field provided.</p>"
-#~ msgstr ""
-#~ "\"报告配置\"对话框使您能够过滤在以前屏幕中选择的报告。要按<b>日期范围</b>"
-#~ "过滤:<br><br> <ol> <li>单击<b>按日期范围过滤</b>。该字段变为活动状态。 "
-#~ "<li>输入描述报告范围的开始和结束日期。 <li>输入其他过滤参数。参考以下的参"
-#~ "数定义。 </ol>以下的定义有助于您在\"报告配置\"对话框中输入过滤参数:<b>程"
-#~ "序名称模式:</b> 当您输入的程序名称或模式与所涉及的可执行进程的名称相匹"
-#~ "配,报告将显示针对特定程序发生的安全性事件。<br><br> <b>设置存档名称模式:"
-#~ "</b>当您输入应用于进程的安全性设置存档名称时,报告将显示针对特定设置存档生"
-#~ "成的安全性事件。由此您可以看到特定设置存档所限制的内容。<br><br> <b>PID "
-#~ "号:</b> 进程 ID 号是一个编号,用来唯一标识某个特定进程或正在运行的程序(此"
-#~ "编号仅在该进程的有效期内有效)。<br><br> <b>严重性级别:</b> 请为您想包含"
-#~ "在报告中的安全性事件选择最低的严重性级别。选定的严重性级别以及在其之上的级"
-#~ "别将包含在报告中。<br><br> <b>细节:</b> 已被设置存档拒绝的访问所针对的"
-#~ "源。 这包含功能和文件。您可以使用此字段,以报告设置存档尚未允许访问的资"
-#~ "源。<br><br> <b>方式:</b>\"方式\"是设置存档授予应用程序或进程并在其上应用"
-#~ "的许可权限。其选项为:r(读取) w(写入) l(链接) x(执行)<br><br> <b>访问类"
-#~ "型:</b> 访问类型描述了安全性事件真正发生的内容。其选项为:允许、拒绝或审"
-#~ "计。<br><br> <b>CSV 或 HTML:</b>可以能够您导出 CSV(逗号分隔值)或 html 文"
-#~ "件。CSV 文件使用标准数据格式,将日志项中的数据片段用逗号分隔开,以便于导入"
-#~ "面向表的应用程序。您可以输入导出报告的路径名,方法是在提供的字段中输入它的"
-#~ "完整路径名。<br><br>"
+#~ msgid "<p>The Report Configuration dialog enables you to filter the report selected in the previous screen. To filter by <b>Date Range:</b><br><br> <ol> <li>Click <b>Filter By Date Range</b>. The fields become active. <li>Enter the start and end dates that delineate the scope of the report. <li>Enter other filtering parameters. See below for definitions of parameters. </ol> The following definitions help you to enter the filtering parameters in the Report Configuration Dialog: <b>Program Name Pattern:</b> When you enter a program name or pattern that matches the name of the executable process of interest, the report will display security events that have occurred for a specific program.<br><br> <b>Profile Name Pattern:</b> When you enter the name of the security profile that is applied to the process, the report will display the security events that are generated for the specified profile. You can use this to see what is being confined by a specific profile.<br><br> <b>PID Num
ber:</b> Process ID number is a number that uniquely identifies one specific process or running program (this number is valid only during the lifetime of that process).<br><br> <b>Severity Level:</b> Select the lowest severity level for security events that you would like to be included in the report. The selected severity level, and above, will be included in the reports.<br><br> <b>Detail:</b> A source to which the profile has denied access. This includes capabilities and files. You can use this field to report the resources are not allowed to be accessed by profiles.<br><br> <b>Mode:</b> The Mode is the permission that the profile grants to the program or process to which it is applied. The options are: r (read) w (write) l (link) x (execute)<br><br> <b>Access Type:</b> The access type describes what is actually happening with the security event. The options are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> Enables you to export a CSV (comma separated values
) or HTML file. The CSV file separates pieces of data in the log entries with commas using a standard data format for importing into table-oriented applications. You can enter a pathname for your exported report by typing in the full pathname in the field provided.</p>"
+#~ msgstr "\"报告配置\"对话框使您能够过滤在以前屏幕中选择的报告。要按<b>日期范围</b>过滤:<br><br> <ol> <li>单击<b>按日期范围过滤</b>。该字段变为活动状态。 <li>输入描述报告范围的开始和结束日期。 <li>输入其他过滤参数。参考以下的参数定义。 </ol>以下的定义有助于您在\"报告配置\"对话框中输入过滤参数:<b>程序名称模式:</b> 当您输入的程序名称或模式与所涉及的可执行进程的名称相匹配,报告将显示针对特定程序发生的安全性事件。<br><br> <b>设置存档名称模式:</b>当您输入应用于进程的安全性设置存档名称时,报告将显示针对特定设置存档生成的安全性事件。由此您可以看到特定设置存档所限制的内容。<br><br> <b>PID 号:</b> 进程 ID 号是一个编号,用来唯一标识某个特定进程或正在运行的程序(此编号仅在该进程的有效期内有效)。<br><br>
<b>严重性级别:</b> 请为您想包含在报告中的安全性事件选择最低的严重性级别。选定的严重性级别以及在其之上的级别将包含在报告中。<br><br> <b>细节:</b> 已被设置存档拒绝的访问所针对的源。 这包含功能和文件。您可以使用此字段,以报告设置存档尚未允许访问的资源。<br><br> <b>方式:</b>\"方式\"是设置存档授予应用程序或进程并在其上应用的许可权限。其选项为:r(读取) w(写入) l(链接) x(执行)<br><br> <b>访问类型:</b> 访问类型描述了安全性事件真正发生的内容。其选项为:允许、拒绝或审计。<br><br> <b>CSV 或 HTML:</b>可以能够您导出 CSV(逗号分隔值)或 html 文件。CSV 文件使用标准数据格式,将日志项中的数据片段用逗号分隔开,以便于导入面向表的应用程序。您可以输入导出报告的路径名,方法是在提供的字段中输入它的完整路径名。<br><
br>"
#, fuzzy
-#~ msgid ""
-#~ "<p>The summary of scheduled reports page shows us when reports are "
-#~ "scheduled to run. Reports can be set to run monthly, weekly, daily, or "
-#~ "hourly. The default settings are daily at midnight. The reports can also "
-#~ "be emailed, upon completion, to up to three email recipients.<br><br> In "
-#~ "the Set Schedule section, you can schedule the following three types of "
-#~ "security reports:<br><br> <b>Executive Security Summary:</b> A combined "
-#~ "report, consisting of one or more Security incident reports from one or "
-#~ "more machines. This report provides a single view of security events on "
-#~ "multiple machines.<br><br> <b>Applications Audit Report:</b> An auditing "
-#~ "tool that reports which application servers are running and whether the "
-#~ "applications are confined by AppArmor. Application servers are "
-#~ "applications that accept incoming network connections. <br><br> "
-#~ "<b>Security Incident Report:</b> A report that displays application "
-#~ "security for a single host. It reports policy violations for locally "
-#~ "confined applications during a specific time period. You can edit and "
-#~ "customize this report, or add new versions.</p>"
-#~ msgstr ""
-#~ "\"日程表报告\"页摘要显示将报告安排在何时运行。可以设置每月、每周、每天或每"
-#~ "小时运行报告一次。默认的设置为每天午夜运行。报告也可以在完成后以电子邮件的"
-#~ "形式发出,最多可以发送给三个收件人。<br><br> 在\"设置日程表\"部分中,您可"
-#~ "以安排以下三种类型安全性报告的日程:<br><br> <b>执行安全性摘要:</b>一份合"
-#~ "成的报告,由来自一台或多台计算机的一份或多份安全性事件报告组成。 此报告使"
-#~ "您能在单个视图中查看多台计算机上的安全性事件。<br><br> <b>应用程序审计报"
-#~ "告:</b>一种审计工具,可以报告正在运行的应用程序服务器及这些应用程序是否"
-#~ "受 AppArmor 限制。应用程序服务器是一组应用程序,它们接受进来的网络连接。"
-#~ "<br><br> <b>安全性事件报告:</b>一份显示单个主机的应用程序安全性的报告。 "
-#~ "报告特定时间段内本地限制的应用程序的策略违例。您可以编辑并自定义该报告,或"
-#~ "添加新的版本。"
+#~ msgid "<p>The summary of scheduled reports page shows us when reports are scheduled to run. Reports can be set to run monthly, weekly, daily, or hourly. The default settings are daily at midnight. The reports can also be emailed, upon completion, to up to three email recipients.<br><br> In the Set Schedule section, you can schedule the following three types of security reports:<br><br> <b>Executive Security Summary:</b> A combined report, consisting of one or more Security incident reports from one or more machines. This report provides a single view of security events on multiple machines.<br><br> <b>Applications Audit Report:</b> An auditing tool that reports which application servers are running and whether the applications are confined by AppArmor. Application servers are applications that accept incoming network connections. <br><br> <b>Security Incident Report:</b> A report that displays application security for a single host. It reports policy violations for locally conf
ined applications during a specific time period. You can edit and customize this report, or add new versions.</p>"
+#~ msgstr "\"日程表报告\"页摘要显示将报告安排在何时运行。可以设置每月、每周、每天或每小时运行报告一次。默认的设置为每天午夜运行。报告也可以在完成后以电子邮件的形式发出,最多可以发送给三个收件人。<br><br> 在\"设置日程表\"部分中,您可以安排以下三种类型安全性报告的日程:<br><br> <b>执行安全性摘要:</b>一份合成的报告,由来自一台或多台计算机的一份或多份安全性事件报告组成。 此报告使您能在单个视图中查看多台计算机上的安全性事件。<br><br> <b>应用程序审计报告:</b>一种审计工具,可以报告正在运行的应用程序服务器及这些应用程序是否受 AppArmor 限制。应用程序服务器是一组应用程序,它们接受进来的网络连接。<br><br> <b>安全性事件报告:</b>一份显示单个主机的应用程序安全性的报告。 报告特定时间段内本地限制的
应用程序的策略违例。您可以编辑并自定义该报告,或添加新的版本。"
-#~ msgid ""
-#~ "<p><b>AppArmor Status</b><br>This reports whether the AppArmor policy "
-#~ "enforcement module is loaded and functioning.</p> <p><b>Security Event "
-#~ "Notification</b><br>Configure this tool if you want to be notified by "
-#~ "email when access violations have occurred.</p> <p><b>Profile Modes"
-#~ "b><br>Use this tool to change the way that AppArmor uses individual "
-#~ "profiles.</p>"
-#~ msgstr ""
-#~ "<p><b>AppArmor 状态</b><br>报告 AppArmor 策略强制模块是否已装载和运作。"
-#~ "p> <p><b>安全性事件通知</b><br>如果想在发生访问违例时通过电子邮件收到通"
-#~ "知,请配置该工具。</p> <p><b>设置存档模式</b><br>使用该工具可更改 "
-#~ "AppArmor 使用单个设置存档的方式。</p>"
+#~ msgid "<p><b>AppArmor Status</b><br>This reports whether the AppArmor policy enforcement module is loaded and functioning.</p> <p><b>Security Event Notification</b><br>Configure this tool if you want to be notified by email when access violations have occurred.</p> <p><b>Profile Modes</b><br>Use this tool to change the way that AppArmor uses individual profiles.</p>"
+#~ msgstr "<p><b>AppArmor 状态</b><br>报告 AppArmor 策略强制模块是否已装载和运作。</p> <p><b>安全性事件通知</b><br>如果想在发生访问违例时通过电子邮件收到通知,请配置该工具。</p> <p><b>设置存档模式</b><br>使用该工具可更改 AppArmor 使用单个设置存档的方式。</p>"
#~ msgid "Email address is too long. Please enter another address."
#~ msgstr "电子邮件地址太长。请输入另一个地址。"
@@ -4037,9 +3476,7 @@
#~ "# 时段:%s 到 %s\n"
#~ "\n"
-#~ msgid ""
-#~ "<tr><th colspan='7'>Executive Security Summary - Generated by AppArmor"
-#~ "th></tr>"
+#~ msgid "<tr><th colspan='7'>Executive Security Summary - Generated by AppArmor</th></tr>"
#~ msgstr "<tr><th colspan='7'>执行安全性摘要 - 由 AppArmor 生成</th></tr>"
#~ msgid "<tr><th colspan='7'>Period: %s to %s</th></tr>\n"
@@ -4055,12 +3492,8 @@
#~ "# 运行日期: %s\n"
#~ "\n"
-#~ msgid ""
-#~ "<table border='1' cellpadding='2'><tr><th colspan='7'>Applications Audit "
-#~ "Report - Generated by AppArmor</th></tr>\n"
-#~ msgstr ""
-#~ "<table border='1' cellpadding='2'><tr><th colspan='7'>应用程序审计报告 - "
-#~ "由 AppArmor 生成</th></tr>\n"
+#~ msgid "<table border='1' cellpadding='2'><tr><th colspan='7'>Applications Audit Report - Generated by AppArmor</th></tr>\n"
+#~ msgstr "<table border='1' cellpadding='2'><tr><th colspan='7'>应用程序审计报告 - 由 AppArmor 生成</th></tr>\n"
#~ msgid "<h4>The following filters were used for report generation:</h4>"
#~ msgstr "<h4>以下过滤器用于生成报告:</h4>"
@@ -4071,8 +3504,7 @@
#~ msgid "<h4>No filters were used for report generation.</h4>"
#~ msgstr "<h4>未使用任何过滤器来生成报告。</h4>"
-#~ msgid ""
-#~ "Fatal Error: Couldn't get report configuration information %s. Exiting."
+#~ msgid "Fatal Error: Couldn't get report configuration information %s. Exiting."
#~ msgstr "致命错误:无法获取报告配置信息 %s。正在退出。"
#~ msgid "Error: Couldn't open (tmp) %s. ESS report execution not tracked."
@@ -4081,20 +3513,16 @@
#~ msgid "Error: Couldn't open %s. ESS report execution not tracked."
#~ msgstr "错误:无法打开 %s。未跟踪 ESS 报告的执行。"
-#~ msgid ""
-#~ "Error: Necessary input missing. Unable to generate report and send mail."
+#~ msgid "Error: Necessary input missing. Unable to generate report and send mail."
#~ msgstr "错误:缺少必要的输入。无法生成报告和发送邮件。"
#~ msgid "Error: Couldn't open %s. No ESS csv report generated."
#~ msgstr "错误:无法打开 %s。未生成 ESS csv 报告。"
-#~ msgid ""
-#~ "<tr bgcolor='edefff'><td>Hostname</td><td>Start Date</td><td>End Date</td>"
-#~ msgstr ""
-#~ "<tr bgcolor='edefff'><td>主机名</td><td>开始日期</td><td>结束日期</td>"
+#~ msgid "<tr bgcolor='edefff'><td>Hostname</td><td>Start Date</td><td>End Date</td>"
+#~ msgstr "<tr bgcolor='edefff'><td>主机名</td><td>开始日期</td><td>结束日期</td>"
-#~ msgid ""
-#~ "<td>Highest Severity</td><td>Mean Severity</td><td>Number of REJECTs</td>"
+#~ msgid "<td>Highest Severity</td><td>Mean Severity</td><td>Number of REJECTs</td>"
#~ msgstr "<td>最高严重性</td><td>一般严重性</td><td>拒绝次数</td>"
#~ msgid "<td>Number of Events</td></tr>\n"
@@ -4109,15 +3537,11 @@
#~ msgid "<h3>Applications Audit Report - Generated by AppArmor</h3>\n"
#~ msgstr "<h3>应用程序审计报告 - 由 AppArmor 生成</h3>\n"
-#~ msgid ""
-#~ "<tr bgcolor='edefff'><td>Hostname</td><td>Date</td><td>Application</td>"
+#~ msgid "<tr bgcolor='edefff'><td>Hostname</td><td>Date</td><td>Application</td>"
#~ msgstr "<tr bgcolor='edefff'><td>主机名</td><td>日期</td><td>应用程序</td>"
-#~ msgid ""
-#~ "<td>Profile</td><td>PID</td><td>State</td><td>AppArmor Profile</td></tr>\n"
-#~ msgstr ""
-#~ "<td>设置存档</td><td>PID</td><td>状态</td><td>AppArmor 设置存档</td>"
-#~ "tr>\n"
+#~ msgid "<td>Profile</td><td>PID</td><td>State</td><td>AppArmor Profile</td></tr>\n"
+#~ msgstr "<td>设置存档</td><td>PID</td><td>状态</td><td>AppArmor 设置存档</td></tr>\n"
#~ msgid "Error: Couldn't open %s. No SIR report generated."
#~ msgstr "错误:无法打开 %s。未生成 SIR 报告。"
--
To unsubscribe, e-mail: opensuse-translation-commit+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-translation-commit+owner@opensuse.org\n"
"<dt>* Virtual server port is 21: ftp\n"
@@ -539,9 +418,7 @@
"\n"
"\n"
"</dt><dt><b><big>check command</big> = \"</b><i>path to script</i><b>\"</b>\n"
-"<p>This setting is used if checktype is external and is the command to be "
-"run to check the status of a real server. It should exit with status 0 if "
-"everything\n"
+"<p>This setting is used if checktype is external and is the command to be run to check the status of a real server. It should exit with status 0 if everything\n"
"is ok, or non-zero otherwise.\n"
"</p><p>Four parameters are passed to the script:\n"
"</p></dt><dt>* virtual server ip/firewall mark\n"
@@ -552,105 +429,68 @@
"\n"
"\n"
"<p><b><big>check port</big> =</b> <i>n</i>\n"
-"</p><p>Number of port to monitor. Sometimes check port differs from service "
-"port.\n"
+"</p><p>Number of port to monitor. Sometimes check port differs from service port.\n"
"</p><p>Default: port specified for each real server\n"
"\n"
"\n"
-"</p><p><b><big>request</big> = \"</b><i>uri to requested object</i><b>\""
-"b>\n"
-"</p><p>This object will be requested each checkinterval seconds on each real "
-"server. The string must be inside quotes. Note that this string may be "
-"overridden by\n"
+"</p><p><b><big>request</big> = \"</b><i>uri to requested object</i><b>\"</b>\n"
+"</p><p>This object will be requested each checkinterval seconds on each real server. The string must be inside quotes. Note that this string may be overridden by\n"
"an optional per real-server based request-string.\n"
-"</p><p>For a <small>DNS</small> check this should the name of an A record, "
-"or the address of a <small>PTR</small> record to look up.\n"
-"</p><p>For a MySQL, Oracle or PostgeSQL check, this should be an <small>SQL"
-"small> query. The data returned is not checked, only that the answer is one "
-"or more\n"
+"</p><p>For a <small>DNS</small> check this should the name of an A record, or the address of a <small>PTR</small> record to look up.\n"
+"</p><p>For a MySQL, Oracle or PostgeSQL check, this should be an <small>SQL</small> query. The data returned is not checked, only that the answer is one or more\n"
"rows. This is a required setting.\n"
-"</p><p>For a simpletcp check, this string is sent verbatim except any "
-"occurances of \n"
+"</p><p>For a simpletcp check, this string is sent verbatim except any occurances of \n"
" are replaced with a new line character.\n"
"\n"
"\n"
"</p><p><b><big>receive</big> = \"</b><i>regexp to compare</i><b>\"</b>\n"
-"</p><p>If the requested result contains this <i>regexp to compare</i>, the "
-"real server is declared alive. The regexp must be inside quotes. Keep in "
-"mind that\n"
-"regexps are not plain strings and that you need to escape the special "
-"characters if they should as literals. Note that this regexp may be "
-"overridden by an\n"
+"</p><p>If the requested result contains this <i>regexp to compare</i>, the real server is declared alive. The regexp must be inside quotes. Keep in mind that\n"
+"regexps are not plain strings and that you need to escape the special characters if they should as literals. Note that this regexp may be overridden by an\n"
"optional per real-server based receive regexp.\n"
-"</p><p>For a <small>DNS</small> check this should be any one the A record's "
-"addresses or any one of the <small>PTR</small> record's names.\n"
+"</p><p>For a <small>DNS</small> check this should be any one the A record's addresses or any one of the <small>PTR</small> record's names.\n"
"</p><p>For a MySQL check, the receive setting is not used.\n"
"\n"
"\n"
-"</p><p><b><big>http method</big> = <small>GET</small></b> | <b><small>HEAD"
-"small></b>\n"
-"</p><p>Sets the <small>HTTP</small> method which should be used to fetch the "
-"<small>URI</small> specified in the request-string. <small>GET</small> is "
-"the\n"
-"method used by default if the parameter is not set. If <small>HEAD</small> "
-"is used, the receive-string should be unset.\n"
+"</p><p><b><big>http method</big> = <small>GET</small></b> | <b><small>HEAD</small></b>\n"
+"</p><p>Sets the <small>HTTP</small> method which should be used to fetch the <small>URI</small> specified in the request-string. <small>GET</small> is the\n"
+"method used by default if the parameter is not set. If <small>HEAD</small> is used, the receive-string should be unset.\n"
"</p><p>Default: <small>GET</small>\n"
"\n"
"\n"
"</p><p><b><big>virtual host</big> = \"</b><i>hostname</i><b>\"</b>\n"
-"</p><p>Used when using a negotiate check with <small>HTTP</small> or "
-"<small>HTTPS</small> . Sets the host header used in the <small>HTTP</small> "
-"request. In the\n"
-"case of <small>HTTPS</small> this generally needs to match the common name "
-"of the <small>SSL</small> certificate. If not set then the host header will "
-"be\n"
-"derived from the request url for the real server if present. As a last "
-"resort the <small>IP</small> address of the real server will be used.\n"
+"</p><p>Used when using a negotiate check with <small>HTTP</small> or <small>HTTPS</small> . Sets the host header used in the <small>HTTP</small> request. In the\n"
+"case of <small>HTTPS</small> this generally needs to match the common name of the <small>SSL</small> certificate. If not set then the host header will be\n"
+"derived from the request url for the real server if present. As a last resort the <small>IP</small> address of the real server will be used.\n"
"\n"
"\n"
"</p><p><b><big>login</big> = \"</b><i>username</i><b>\"</b>\n"
-"</p><p>For <small>FTP</small> , <small>IMAP</small> , <small>LDAP</small> , "
-"MySQL, Oracle, <small>POP</small> and PostgreSQL, the username used to log "
-"in.\n"
+"</p><p>For <small>FTP</small> , <small>IMAP</small> , <small>LDAP</small> , MySQL, Oracle, <small>POP</small> and PostgreSQL, the username used to log in.\n"
"</p><p>For Radius the passwd is used for the attribute User-Name.\n"
-"</p><p>For <small>SIP</small> , the username is used as both the to and from "
-"address for an <small>OPTIONS</small> query.\n"
+"</p><p>For <small>SIP</small> , the username is used as both the to and from address for an <small>OPTIONS</small> query.\n"
"</p><p>Default:\n"
"</p></dt><dt>* <small>FTP:</small> Anonymous\n"
-"</dt><dt>* MySQL Oracle, and PostgreSQL: Must be specified in the "
-"configuration\n"
-"</dt><dt>* <small>SIP:</small> ldirectord@<hostname>, hostname is "
-"derived as per the passwd option below.\n"
-"</dt><dt>* Otherwise: empty string, which denotes that case authentication "
-"will not be attempted.\n"
+"</dt><dt>* MySQL Oracle, and PostgreSQL: Must be specified in the configuration\n"
+"</dt><dt>* <small>SIP:</small> ldirectord@<hostname>, hostname is derived as per the passwd option below.\n"
+"</dt><dt>* Otherwise: empty string, which denotes that case authentication will not be attempted.\n"
"\n"
"\n"
"</dt><dt><b><big>password</big> = \"</b><i>password</i><b>\"</b>\n"
-"<p>Password to use to login to <small>FTP</small> , <small>IMAP</small> , "
-"<small>LDAP</small> , MySQL, Oracle, <small>POP</small> , PostgreSQL and\n"
+"<p>Password to use to login to <small>FTP</small> , <small>IMAP</small> , <small>LDAP</small> , MySQL, Oracle, <small>POP</small> , PostgreSQL and\n"
"<small>SIP</small> servers.\n"
"</p><p>For Radius the passwd is used for the attribute User-Password.\n"
"</p><p>Default:\n"
-"</p></dt><dt>* <small>FTP:</small> ldirectord@<hostname>, where "
-"hostname is the environment variable <small>HOSTNAME</small> evaluated at "
-"run time, or sourced\n"
+"</p></dt><dt>* <small>FTP:</small> ldirectord@<hostname>, where hostname is the environment variable <small>HOSTNAME</small> evaluated at run time, or sourced\n"
"from uname if unset.\n"
-"</dt><dt>* Otherwise: empty string. In the case of <small>LDAP</small> , "
-"MySQL, Oracle, and PostgreSQL this means that authentication will not be "
-"performed.\n"
+"</dt><dt>* Otherwise: empty string. In the case of <small>LDAP</small> , MySQL, Oracle, and PostgreSQL this means that authentication will not be performed.\n"
"\n"
"\n"
"</dt><dt><b><big>database name</big> = \"</b><i>databasename</i><b>\"</b>\n"
-"<p>Database to use for MySQL, Oracle and PostgreSQL servers, this is the "
-"database that the query (set by <b>receive</b> above) will be performed "
-"against. This\n"
+"<p>Database to use for MySQL, Oracle and PostgreSQL servers, this is the database that the query (set by <b>receive</b> above) will be performed against. This\n"
"is a required setting.\n"
"\n"
"\n"
"</p><p><b><big>radius secret</big> = \"</b><i>radiussecret</i><b>\"</b>\n"
-"</p><p>Secret to use for Radius servers, this is the secret used to perform "
-"an Access-Request with the username (set by <b>login</b> above) and passwd "
-"(set by\n"
+"</p><p>Secret to use for Radius servers, this is the secret used to perform an Access-Request with the username (set by <b>login</b> above) and passwd (set by\n"
"<b>passwd</b> above).\n"
"</p><p>Default: empty string\n"
"\n"
@@ -664,137 +504,87 @@
"\n"
"\n"
"</p><p><b><big>scheduler</big> =</b> <i>scheduler_name</i>\n"
-"</p><p>Scheduler to be used by <small>LVS</small> for loadbalancing. For an "
-"information on the available sehedulers please see the <b>ipvsadm</a></b>(8) man page.\n"
+"</p><p>Scheduler to be used by <small>LVS</small> for loadbalancing. For an information on the available sehedulers please see the <b>ipvsadm</a></b>(8) man page.\n"
"</p><p>Default: \"wrr\"\n"
"\n"
"\n"
"</p><p><b><big>protocol</big> = tcp</b>|<b>udp</b>|<b>fwm</b>\n"
-"</p><p>Protocol to be used. If the virtual is specified as an <small>IP"
-"small> address and port then it must be one of tcp or udp. If a firewall "
-"mark then the\n"
+"</p><p>Protocol to be used. If the virtual is specified as an <small>IP</small> address and port then it must be one of tcp or udp. If a firewall mark then the\n"
"protocol must be fwm.\n"
"</p><p>Default:\n"
-"</p></dt><dt>* Virtual is an <small>IP</small> address and port, and the "
-"port is not 53: tcp\n"
-"</dt><dt>* Virtual is an <small>IP</small> address and port, and the port is "
-"53: udp\n"
+"</p></dt><dt>* Virtual is an <small>IP</small> address and port, and the port is not 53: tcp\n"
+"</dt><dt>* Virtual is an <small>IP</small> address and port, and the port is 53: udp\n"
"</dt><dt>* Virtual is a firewall mark: fwm\n"
"</dt></dl>\n"
"\n"
"\n"
"</p><p><b><big>check timeout</big> =</b> <i>n</i>\n"
-"</p><p>Timeout in seconds for connect, external and ping checks. If the "
-"timeout is exceeded then the real server is declared dead.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
-"</p><p>If undefined then the value of negotiatetimeout is used. "
-"negotiatetimeout is also a global value that may be overriden by a per-"
-"virtual setting.\n"
-"</p><p>If both checktimeout and negotiatetimeout are unset, the default is "
-"used.\n"
+"</p><p>Timeout in seconds for connect, external and ping checks. If the timeout is exceeded then the real server is declared dead.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
+"</p><p>If undefined then the value of negotiatetimeout is used. negotiatetimeout is also a global value that may be overriden by a per-virtual setting.\n"
+"</p><p>If both checktimeout and negotiatetimeout are unset, the default is used.\n"
"</p><p>Default: 5 seconds\n"
"\n"
"</p><p><b><big>negotiate timeout</big> =</b> <i>n</i>\n"
"</p><p>Timeout in seconds for negotiate checks.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
-"</p><p>If undefined then the value of connecttimeout is used. connecttimeout "
-"is also a global value that may be overriden by a per-virtual setting.\n"
-"</p><p>If both negotiatetimeout and connecttimeout are unset, the default is "
-"used.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
+"</p><p>If undefined then the value of connecttimeout is used. connecttimeout is also a global value that may be overriden by a per-virtual setting.\n"
+"</p><p>If both negotiatetimeout and connecttimeout are unset, the default is used.\n"
"</p><p>Default: 30 seconds\n"
"\n"
"</p><p><b><big>failure count</big> =</b> <i>n</i>\n"
-"</p><p>The number of consecutive times a failure will have to be reported by "
-"a check before the realserver is considered to have failed. A value of 1 "
-"will have the realserver considered failed on the first failure. A "
-"successful check will reset the failure counter to 0.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p>The number of consecutive times a failure will have to be reported by a check before the realserver is considered to have failed. A value of 1 will have the realserver considered failed on the first failure. A successful check will reset the failure counter to 0.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"</p><p>Default: 1\n"
"\n"
"</p><p><b><big>email alert</big> = \"</b><i>emailaddress</i><b>\"</b>\n"
-"</p><p>A valid email address for sending alerts about the changed connection "
-"status to any real server defined in the virtual service. This option "
-"requires perl\n"
-"module MailTools to be installed. Automatically tries to send email using "
-"any of the built-in methods. See perldoc Mail::Mailer for more info on "
-"methods.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p>A valid email address for sending alerts about the changed connection status to any real server defined in the virtual service. This option requires perl\n"
+"module MailTools to be installed. Automatically tries to send email using any of the built-in methods. See perldoc Mail::Mailer for more info on methods.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"\n"
"</p><p><b><big>email alert freq</big> =</b> <i>n</i>\n"
-"</p><p>Delay in seconds between repeating email alerts while any given real "
-"server in the virtual service remains inaccessible. A setting of zero "
-"seconds will\n"
-"inhibit the repeating alerts. The email timing accuracy of this setting is "
-"dependent on the number of seconds defined in the checkinterval "
-"configuration\n"
+"</p><p>Delay in seconds between repeating email alerts while any given real server in the virtual service remains inaccessible. A setting of zero seconds will\n"
+"inhibit the repeating alerts. The email timing accuracy of this setting is dependent on the number of seconds defined in the checkinterval configuration\n"
"option.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"</p><p>Default: 0\n"
"\n"
-"</p><p><b><big>email alert status</big> = all</b>|<b>none</b>|<b>starting"
-"b>|<b>running</b>|<b>stopping</b>|<b>reloading</b>,...\n"
-"</p><p>Comma delimited list of server states in which email alerts should be "
-"sent. <b>all</b> is a short-hand for\n"
-"\"<b>starting</b>,<b>running</b>,<b>stopping</b>,<b>reloading</b>\". If "
-"<b>none</b> is specified, no other option may be specified, otherwise "
-"options are ORed\n"
+"</p><p><b><big>email alert status</big> = all</b>|<b>none</b>|<b>starting</b>|<b>running</b>|<b>stopping</b>|<b>reloading</b>,...\n"
+"</p><p>Comma delimited list of server states in which email alerts should be sent. <b>all</b> is a short-hand for\n"
+"\"<b>starting</b>,<b>running</b>,<b>stopping</b>,<b>reloading</b>\". If <b>none</b> is specified, no other option may be specified, otherwise options are ORed\n"
"with each other.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"</p><p>Default: all\n"
"\n"
-"</p><p><b><big>fallback</big> =</b> <i>ip_address|hostname[:portnumber|"
-"sercvicename]</i> [<b>gate</b>|<b>masq</b>|<b>ipip</b>]\n"
-"</p><p>the server onto which a webservice is redirected if all real servers "
-"are down. Typically this would be 127.0.0.1 with an emergency page.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p><b><big>fallback</big> =</b> <i>ip_address|hostname[:portnumber|sercvicename]</i> [<b>gate</b>|<b>masq</b>|<b>ipip</b>]\n"
+"</p><p>the server onto which a webservice is redirected if all real servers are down. Typically this would be 127.0.0.1 with an emergency page.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"\n"
"</p><p><b><big>quiescent</big> = yes</b>|<b>no</b>\n"
-"</p><p>If <i>yes</i>, then when real or failback servers are determined to "
-"be down, they are not actually removed from the kernel's <small>LVS</small> "
-"table.\n"
-"Rather, their weight is set to zero which means that no new connections will "
-"be accepted.\n"
-"</p><p>This has the side effect, that if the real server has persistent "
-"connections, new connections from any existing clients will continue to be "
-"routed to the\n"
-"real server, until the persistant timeout can expire. See ipvsadm for more "
-"information on persistant connections.\n"
+"</p><p>If <i>yes</i>, then when real or failback servers are determined to be down, they are not actually removed from the kernel's <small>LVS</small> table.\n"
+"Rather, their weight is set to zero which means that no new connections will be accepted.\n"
+"</p><p>This has the side effect, that if the real server has persistent connections, new connections from any existing clients will continue to be routed to the\n"
+"real server, until the persistant timeout can expire. See ipvsadm for more information on persistant connections.\n"
"</p><p>This side-effect can be avoided by running the following:\n"
"</p><p>echo 1 > /proc/sys/net/ipv4/vs/expire_quiescent_template\n"
-"</p><p>If the proc file isn't present this probably means that the kernel "
-"doesn't have lvs support, <small>LVS</small> support isn't loaded, or the "
-"kernel is too\n"
-"old to have the proc file. Running ipvsadm as root should load <small>LVS"
-"small> into the kernel if it is possible.\n"
-"</p><p>If <i>no</i>, then the real or failback servers will be removed from "
-"the kernel's <small>LVS</small> table. The default is <i>yes</i>.\n"
-"</p><p>If defined in a virtual server section then the global value is "
-"overridden.\n"
+"</p><p>If the proc file isn't present this probably means that the kernel doesn't have lvs support, <small>LVS</small> support isn't loaded, or the kernel is too\n"
+"old to have the proc file. Running ipvsadm as root should load <small>LVS</small> into the kernel if it is possible.\n"
+"</p><p>If <i>no</i>, then the real or failback servers will be removed from the kernel's <small>LVS</small> table. The default is <i>yes</i>.\n"
+"</p><p>If defined in a virtual server section then the global value is overridden.\n"
"</p><p>Default: <i>yes</i>\n"
"\n"
"\n"
"\n"
msgstr ""
"\n"
-"<p><b><big>virtual server</big> =</b> <i>(IP 地址|主机名:端口号|"
-"服务名)|防火墙标记</i>\n"
+"<p><b><big>virtual server</big> =</b> <i>(IP 地址|主机名:端口号|服务名)|防火墙标记</i>\n"
"</p><p>通过 IP 地址 (或主机名) 和端口 (或服务名) 或防火墙标记定义了一个虚拟服务。\n"
"防火墙标记是一个大于零的整数。标记数据包配置由 <b>ipchains</b>(8) 的 <tt>\"-m\"</tt> 选项控制。\n"
"某个虚拟服务的全部真实服务和旗标必须紧随此行并缩进。\n"
"\n"
"\n"
-"</p><p><b><big>real servers</big> =</b> <i>IP 地址|主机名[->"
-"IP 地址|主机名][:端口号|服务名</i>]\n"
-"<b>gate</b>|<b>masq</b>|<b>ipip</b> [<i>权重</i>] [<b>\"</b><i>request"
-"i><b>\", \"</b><i>receive</i><b>\"</b>]\n"
+"</p><p><b><big>real servers</big> =</b> <i>IP 地址|主机名[->IP 地址|主机名][:端口号|服务名</i>]\n"
+"<b>gate</b>|<b>masq</b>|<b>ipip</b> [<i>权重</i>] [<b>\"</b><i>request</i><b>\", \"</b><i>receive</i><b>\"</b>]\n"
"</p><p>通过 IP 地址 (或主机名) 和端口 (或服务名) 定义了一个真实服务。\n"
"若省略端口则将使用 0,这主要用意是为了 fwmark 服务,它会忽略真实服务器的端口。\n"
"可选地也可赋予一段 <small>IP</small> 地址 (或两个主机名), 在这种情况下将用给定端口测试\n"
@@ -811,13 +601,11 @@
"虚拟服务的端口。即,端口映射仅当真实服务器是另外一台机器且\n"
"转发方式为 masq 时才可用。这是由于内核函数中的相关 <small>LVS</small> 代码的写法导致的。\n"
"</p><p>一个虚拟服务器部分可以有多于一个这样的项。\n"
-"上面列出的 checktimeout, negotiatetimeout, failurecount, fallback, emailalert, "
-"emailalertfreq 和\n"
+"上面列出的 checktimeout, negotiatetimeout, failurecount, fallback, emailalert, emailalertfreq 和\n"
"quiescent 选项也可在虚拟服务器部分出现,那样将覆盖全局设置。\n"
"\n"
"\n"
-"</p><p><b><big>check type</big> = connect</b>|<b>external</b>|<b>negotiate"
-"b>|<b>off</b>|<b>on</b>|<b>ping</b>|<b>检查超时</b><i>N</i>\n"
+"</p><p><b><big>check type</big> = connect</b>|<b>external</b>|<b>negotiate</b>|<b>off</b>|<b>on</b>|<b>ping</b>|<b>检查超时</b><i>N</i>\n"
"</p><p>要执行的检查类型。协商会发送一个请求并匹配收到的字符串。\n"
"连接仅尝试进行一次 <small>TCP/IP</small> 连接,因此发送和接收的字符串可能会被省略。\n"
"若检查类型为一个数字则将混合协商和连接,以便每执行 N 次连接尝试后执行一次协商尝试。\n"
@@ -829,14 +617,10 @@
"默认是 <i>negotiate</i>。\n"
"\n"
"\n"
-"</p><p><b><big>service</big> = dns</b>|<b>ftp</b>|<b>http</b>|<b>https</b>|"
-"<b>imap</b>|<b>imaps</b>|<b>ldap</b>|<b>mysql</b>|<b>nntp</b>|<b>none</b>|"
-"<b>oracle</b>|<b>pgsql</b>|<b>pop</b>|<b>pops</b>|<b>radius</b>|"
-"<b>simpletcp</b>|<b>sip</b>|<b>smtp</b>\n"
+"</p><p><b><big>service</big> = dns</b>|<b>ftp</b>|<b>http</b>|<b>https</b>|<b>imap</b>|<b>imaps</b>|<b>ldap</b>|<b>mysql</b>|<b>nntp</b>|<b>none</b>|<b>oracle</b>|<b>pgsql</b>|<b>pop</b>|<b>pops</b>|<b>radius</b>|<b>simpletcp</b>|<b>sip</b>|<b>smtp</b>\n"
"</p><p>当所用的检查类型为 negotiate 时要监视的服务类型。\n"
"None 表示将不监视服务。\n"
-"</p><p>simpletcp 将发送 <b>request</b> 字符串到服务器并将返回结果与"
-" <b>receive</b> 正则表达式进行匹配测试。\n"
+"</p><p>simpletcp 将发送 <b>request</b> 字符串到服务器并将返回结果与 <b>receive</b> 正则表达式进行匹配测试。\n"
"其它类型的检查会使用特定协议连接服务器。\n"
"协议相关信息请参考 <b>request</b> 和 <b>receive</b> 部分。\n"
"</p><p>默认:\n"
@@ -876,14 +660,10 @@
"</p><p>默认: 指派给每个真实服务器的端口\n"
"\n"
"\n"
-"</p><p><b><big>request</big> = \"</b><i>所请求对象的 uri</i><b>\""
-"b>\n"
-"</p><p>每过 checkinterval 秒将在每个真实服务器上请求此对象。"
-"该字符串必须括起来。注意此字符串可能被可选的基于单个真实服务器的请求字符串覆盖。\n"
-"</p><p>对于 <small>DNS</small> 检查这应为一个 A 记录的名称,"
-"或 <small>PTR</small> 记录的地址才能查询。\n"
-"</p><p>对于 MySQL、Oracle 或 PostgeSQL 检查这应为一条 <small>SQL"
-"small> 查询。返回数据不做检查,仅检查回应是否为一个或多个列。\n"
+"</p><p><b><big>request</big> = \"</b><i>所请求对象的 uri</i><b>\"</b>\n"
+"</p><p>每过 checkinterval 秒将在每个真实服务器上请求此对象。该字符串必须括起来。注意此字符串可能被可选的基于单个真实服务器的请求字符串覆盖。\n"
+"</p><p>对于 <small>DNS</small> 检查这应为一个 A 记录的名称,或 <small>PTR</small> 记录的地址才能查询。\n"
+"</p><p>对于 MySQL、Oracle 或 PostgeSQL 检查这应为一条 <small>SQL</small> 查询。返回数据不做检查,仅检查回应是否为一个或多个列。\n"
"这是一个必需的设置。\n"
"</p><p>对于 simpletcp 检查,此字符串将逐字发送,除了出现的空格会被替换为表示新行的字符。\n"
"\n"
@@ -897,8 +677,7 @@
"</p><p>对于 MySQL 检查不会使用接收设置。\n"
"\n"
"\n"
-"</p><p><b><big>http method</big> = <small>GET</small></b> | <b><small>HEAD"
-"small></b>\n"
+"</p><p><b><big>http method</big> = <small>GET</small></b> | <b><small>HEAD</small></b>\n"
"</p><p>设置应用于撷取在请求字符串中指定的 <small>URI</small> 的 <small>HTTP</small> 方法。\n"
"<small>GET</small> 是未设置参数时的默认方法。\n"
"若使用了 <small>HEAD</small> 则应取消接收字符串的设置。\n"
@@ -909,45 +688,35 @@
"</p><p>当使用带 <small>HTTP</small> 或 <small>HTTPS</small> 的 negotiate 检查时所用。\n"
"其设置了 <small>HTTP</small> 请求中所用的主机头部。\n"
"在 <small>HTTPS</small> 的情况下这一般需要匹配 <small>SSL</small> 证书的通用名。\n"
-"若未设置则将从可能存在的真实服务器的请求 URL 中提取主机头部。"
-"最后一招是使用真实服务器的 <small>IP</small> 地址。\n"
+"若未设置则将从可能存在的真实服务器的请求 URL 中提取主机头部。最后一招是使用真实服务器的 <small>IP</small> 地址。\n"
"\n"
"\n"
"</p><p><b><big>login</big> = \"</b><i>用户名</i><b>\"</b>\n"
-"</p><p>对于 <small>FTP</small>、<small>IMAP</small>、<small>LDAP</small>、"
-"MySQL、Oracle、<small>POP</small> 和 PostgreSQL 来说,该用户名将用于登入。\n"
+"</p><p>对于 <small>FTP</small>、<small>IMAP</small>、<small>LDAP</small>、MySQL、Oracle、<small>POP</small> 和 PostgreSQL 来说,该用户名将用于登入。\n"
"</p><p>对于 Radius 将使用密码作为 User-Name 属性\n"
-"</p><p>对于 <small>SIP</small>,该用户名将用作 <small>OPTIONS</small> 查询的 to 和 from "
-"地址。\n"
+"</p><p>对于 <small>SIP</small>,该用户名将用作 <small>OPTIONS</small> 查询的 to 和 from 地址。\n"
"</p></dt><dt>* <small>FTP:</small> Anonymous\n"
"</dt><dt>* MySQL、Oracle 和 PostgreSQL: 必须在配置中有所指定\n"
-"</dt><dt>* <small>SIP:</small> ldirectord@<hostname>,hostname 从下面的 "
-"passwd 选项中提取。\n"
+"</dt><dt>* <small>SIP:</small> ldirectord@<hostname>,hostname 从下面的 passwd 选项中提取。\n"
"</dt><dt>* 其它: 空字符串,表示不尝试认证。\n"
"\n"
"\n"
"</dt><dt><b><big>password</big> = \"</b><i>密码</i><b>\"</b>\n"
-"<p>用于登入到 <small>FTP</small>、<small>IMAP</small>、"
-"<small>LDAP</small> 、MySQL、Oracle、<small>POP</small>、PostgreSQL 和\n"
+"<p>用于登入到 <small>FTP</small>、<small>IMAP</small>、<small>LDAP</small> 、MySQL、Oracle、<small>POP</small>、PostgreSQL 和\n"
"<small>SIP</small> 服务器的密码。\n"
"</p><p>对于 Radius 该密码用作 User-Password 属性\n"
"</p><p>默认:\n"
-"</p></dt><dt>* <small>FTP:</small> ldirectord@<hostname>,主机名是运行时评估出的"
-"环境变量 <small>HOSTNAME</small>,或者若未设置则从 uname 中提炼出来。\n"
-"</dt><dt>* 其它: 空字符串。在 <small>LDAP</small>、"
-"MySQL、Oracle 和 PostgreSQL 的情况下这意味着将不执行认证。\n"
+"</p></dt><dt>* <small>FTP:</small> ldirectord@<hostname>,主机名是运行时评估出的环境变量 <small>HOSTNAME</small>,或者若未设置则从 uname 中提炼出来。\n"
+"</dt><dt>* 其它: 空字符串。在 <small>LDAP</small>、MySQL、Oracle 和 PostgreSQL 的情况下这意味着将不执行认证。\n"
"\n"
"\n"
"</dt><dt><b><big>database name</big> = \"</b><i>数据库名称</i><b>\"</b>\n"
-"<p>用于 MySQL、Oracle 和 PostgreSQL 服务器的数据库,这是执行查询"
-" (由上面的 <b>receive</b> 设置) 的数据库。\n"
+"<p>用于 MySQL、Oracle 和 PostgreSQL 服务器的数据库,这是执行查询 (由上面的 <b>receive</b> 设置) 的数据库。\n"
"这是一个必需的设置。\n"
"\n"
"\n"
"</p><p><b><big>radius secret</big> = \"</b><i>radius 密码</i><b>\"</b>\n"
-"</p><p>用于 Radius 服务器的密码。这是与用户名 (由上面的 <b>login</b> 设置) 和密码 "
-"(由上面的"
-"<b>passwd</b> 设置) 一起执行访问请求所用的密码。\n"
+"</p><p>用于 Radius 服务器的密码。这是与用户名 (由上面的 <b>login</b> 设置) 和密码 (由上面的<b>passwd</b> 设置) 一起执行访问请求所用的密码。\n"
"</p><p>默认: 空字符串\n"
"\n"
"\n"
@@ -961,14 +730,12 @@
"\n"
"</p><p><b><big>scheduler</big> =</b> <i>scheduler_name</i>\n"
"</p><p>被 <small>LVS</small> 用于负载平衡的计划器。\n"
-"可用计划器信息请参考 <b>ipvsadm</a></b>(8) 手册页。\n"
+"可用计划器信息请参考 <b>ipvsadm</a></b>(8) 手册页。\n"
"</p><p>默认: \"wrr\"\n"
"\n"
"\n"
"</p><p><b><big>protocol</big> = tcp</b>|<b>udp</b>|<b>fwm</b>\n"
-"</p><p>要使用的协议。若 virtual 被指定为 <small>IP"
-"small> 地址和端口则其必须是 tcp 或 udp 之一,若是防火墙标记则协议必须是 fwm。\n"
+"</p><p>要使用的协议。若 virtual 被指定为 <small>IP</small> 地址和端口则其必须是 tcp 或 udp 之一,若是防火墙标记则协议必须是 fwm。\n"
"</p><p>默认:\n"
"</p></dt><dt>* Virtual 是 <small>IP</small> 地址和端口,且端口不是 53: tcp\n"
"</dt><dt>* Virtual 是 <small>IP</small> 地址和端口,且端口是 53: udp\n"
@@ -977,11 +744,10 @@
"\n"
"\n"
"</p><p><b><big>check timeout</big> =</b> <i>n</i>\n"
-"</p><p>用于 connect、external 和 ping 检查的超时秒数。\nchecks. If the "
-"若超时则宣称真实服务器已死。\n"
+"</p><p>用于 connect、external 和 ping 检查的超时秒数。\n"
+"checks. If the 若超时则宣称真实服务器已死。\n"
"</p><p>若定义在虚拟服务器部分则将覆盖全局值。\n"
-"</p><p>若未定义则使用 negotiatetimeout 值。"
-"negotiatetimeout 也是一个可为单一虚拟服务器设置覆盖的全局值。\n"
+"</p><p>若未定义则使用 negotiatetimeout 值。negotiatetimeout 也是一个可为单一虚拟服务器设置覆盖的全局值。\n"
"</p><p>若 checktimeout 和 negotiatetimeout 均未设置则用默认。\n"
"</p><p>默认: 5 秒\n"
"\n"
@@ -1013,17 +779,14 @@
"</p><p>若定义在虚拟服务器部分则将覆盖全局值。\n"
"</p><p>默认: 0\n"
"\n"
-"</p><p><b><big>email alert status</big> = all</b>|<b>none</b>|<b>starting"
-"b>|<b>running</b>|<b>stopping</b>|<b>reloading</b>,...\n"
+"</p><p><b><big>email alert status</big> = all</b>|<b>none</b>|<b>starting</b>|<b>running</b>|<b>stopping</b>|<b>reloading</b>,...\n"
"</p><p>逗号划分的应发送邮件提醒的服务器状态列表。\n"
-"<b>all</b> 是针对 \"<b>starting</b>,<b>running</b>,<b>stopping</b>,<b>reloading<"
-"/b>\" 的简写。\n"
+"<b>all</b> 是针对 \"<b>starting</b>,<b>running</b>,<b>stopping</b>,<b>reloading</b>\" 的简写。\n"
"若指定 <b>none</b> 则不会指定其它任何选项,否则选项间是「或」 的关系。\n"
"</p><p>若定义在虚拟服务器部分则将覆盖全局值。\n"
"</p><p>默认: all\n"
"\n"
-"</p><p><b><big>fallback</big> =</b> <i>IP 地址|主机名[:端口号|"
-"服务名]</i> [<b>gate</b>|<b>masq</b>|<b>ipip</b>]\n"
+"</p><p><b><big>fallback</big> =</b> <i>IP 地址|主机名[:端口号|服务名]</i> [<b>gate</b>|<b>masq</b>|<b>ipip</b>]\n"
"</p><p>若全部真实服务器均离线时网络服务将中转到的服务器。\n"
"通常这将是带有紧急公告页面的 127.0.0.1。\n"
"</p><p>若定义在虚拟服务器部分则将覆盖全局值。\n"
@@ -1036,8 +799,7 @@
"</p><p>此副作用可通过运行如下命令避免:\n"
"</p><p>echo 1 > /proc/sys/net/ipv4/vs/expire_quiescent_template\n"
"</p><p>若该 proc 文件不存在这可能意味着内核没有 lvs 支持、<small>LVS</small> 支持未加载,\n"
-"或内核太老完全没有该 proc 文件。若可行以 root 身份运行 ipvsadm 应能加载 <small>LVS"
-"small> 到内核。\n"
+"或内核太老完全没有该 proc 文件。若可行以 root 身份运行 ipvsadm 应能加载 <small>LVS</small> 到内核。\n"
"</p><p>若为 <i>no</i> 则真实或回退服务器将从内核的 <small>LVS</small> 表中移除。默认为 <i>yes</i>。\n"
"</p><p>若定义在虚拟服务器部分则将覆盖全局值。\n"
"</p><p>默认: <i>yes</i>\n"
@@ -1258,5 +1020,3 @@
#: src/modules/Iplb.rb:441
msgid "Configuration summary..."
msgstr "配置摘要..."
-
-
Modified: trunk/yast/zh_CN/po/iscsi-client.zh_CN.po
===================================================================
--- trunk/yast/zh_CN/po/iscsi-client.zh_CN.po 2014-10-07 15:48:22 UTC (rev 89783)
+++ trunk/yast/zh_CN/po/iscsi-client.zh_CN.po 2014-10-07 15:49:12 UTC (rev 89784)
@@ -332,8 +332,7 @@
#. table of connected targets
#: src/include/iscsi-client/helps.rb:90
msgid ""
-"List of current sessions. To add a new target, select it and press <b>Add"
-"b>.\n"
+"List of current sessions. To add a new target, select it and press <b>Add</b>.\n"
"To remove it, press <b>Log Out</b>.\n"
"To change the start-up status, press <b>Toggle</b>.\n"
msgstr ""
@@ -348,57 +347,41 @@
msgstr "<h1>警告</h1>"
#: src/include/iscsi-client/helps.rb:97 src/include/iscsi-client/helps.rb:115
-msgid ""
-"<p>When accessing an iSCSI device <b>READ</b>/<b>WRITE</b>, make sure that "
-"this access is exclusive. Otherwise there is a potential risk of data "
-"corruption.</p>\n"
-msgstr ""
-"<p>当<b>读</b>/<b>写</b>访问一个 iSCSI 设备时,请确保此访问是排它的。否则会有"
-"潜在的数据损坏风险。</p>\n"
+msgid "<p>When accessing an iSCSI device <b>READ</b>/<b>WRITE</b>, make sure that this access is exclusive. Otherwise there is a potential risk of data corruption.</p>\n"
+msgstr "<p>当<b>读</b>/<b>写</b>访问一个 iSCSI 设备时,请确保此访问是排它的。否则会有潜在的数据损坏风险。</p>\n"
#: src/include/iscsi-client/helps.rb:100
msgid ""
-"<p><b>InitiatorName</b> is a value from <tt>/etc/iscsi/initiatorname.iscsi"
-"tt>. \n"
-"In case you have iBFT, this value will be added from there and you are only "
-"able to change it in the BIOS setup.</p>"
+"<p><b>InitiatorName</b> is a value from <tt>/etc/iscsi/initiatorname.iscsi</tt>. \n"
+"In case you have iBFT, this value will be added from there and you are only able to change it in the BIOS setup.</p>"
msgstr ""
"<p><b>发起端名称</b> 是 <tt>/etc/initiatorname.iscsi</tt> 中的一个值。\n"
"若您有 iBFT,此值将从那里添加,并且您只能在 BIOS 设置中修改它。</p>"
#: src/include/iscsi-client/helps.rb:103
msgid ""
-"If you want to use <b>iSNS</b> (Internet Storage Name Service) for "
-"discovering targets instead of the default SendTargets method,\n"
-"fill in the IP address of the iSNS server and port. The default port should "
-"be 3205.\n"
+"If you want to use <b>iSNS</b> (Internet Storage Name Service) for discovering targets instead of the default SendTargets method,\n"
+"fill in the IP address of the iSNS server and port. The default port should be 3205.\n"
msgstr ""
-"若您想用 <b>iSNS</b> (互联网存储名称服务) 来发现目标,而不是用默认的 "
-"SendTargets 方法,\n"
+"若您想用 <b>iSNS</b> (互联网存储名称服务) 来发现目标,而不是用默认的 SendTargets 方法,\n"
"请填上 iSNS 服务器的 IP 地址和端口。默认端口应是 3205。\n"
#: src/include/iscsi-client/helps.rb:108
msgid ""
"Enter the <b>IP Address</b> of the discovered server.\n"
-"Only change <b>Port</b> if needed. For authentication, use <b>Username</b> "
-"and <b>Password</b>. If you do not need authentication,\n"
+"Only change <b>Port</b> if needed. For authentication, use <b>Username</b> and <b>Password</b>. If you do not need authentication,\n"
"select <b>No Authentication</b>.\n"
msgstr ""
"请输入已发现的服务器的 <b>IP 地址</b>。\n"
-"只有需要时才能修改<b>端口</b>。若需要认证,请使用<b>用户名</b>和<b>密码</b>。"
-"若无需认证,\n"
+"只有需要时才能修改<b>端口</b>。若需要认证,请使用<b>用户名</b>和<b>密码</b>。若无需认证,\n"
"请选择<b>无认证</b>。\n"
#: src/include/iscsi-client/helps.rb:122
-msgid ""
-"List of nodes offered by the iSCSI target. Select one item and click "
-"<b>Connect</b>. "
+msgid "List of nodes offered by the iSCSI target. Select one item and click <b>Connect</b>. "
msgstr "iSCSI 目标提供的节点列表。请选择一项并按<b>连接</b>。"
#: src/include/iscsi-client/helps.rb:129
-msgid ""
-"Select the type of authentication and enter the <b>Username</b> and "
-"<b>Password</b>."
+msgid "Select the type of authentication and enter the <b>Username</b> and <b>Password</b>."
msgstr "选择认证类型并输入<b>用户名</b>和<b>密码</b>。"
#: src/include/iscsi-client/helps.rb:132
@@ -409,23 +392,18 @@
msgid ""
"<p><b>manual</b> is for iSCSI targets which are not to be connected by\n"
"default, the user needs to connect them manually</p>\n"
-"<p><b>onboot</b> is for iSCSI targets to be connected during boot, i.e. "
-"when\n"
+"<p><b>onboot</b> is for iSCSI targets to be connected during boot, i.e. when\n"
"root is on iSCSI. As such it will be evaluated by the initrd.</p>\n"
-"<p><b>automatic</b> is for iSCSI targets to be connected when the iSCSI "
-"service\n"
+"<p><b>automatic</b> is for iSCSI targets to be connected when the iSCSI service\n"
"starts up.</p>\n"
msgstr ""
"<p><b>手动</b>用于默认不连接的 iSCSI 目标,用户需要手动连接它们</p>\n"
-"<p><b>引导时</b>用于在引导时连接的 iSCSI 目标,例如,当 root 在 iSCSI 上时。"
-"因为这样 initrd 就需要评估位于 iSCSI 上的 root 分区了。</p>\n"
+"<p><b>引导时</b>用于在引导时连接的 iSCSI 目标,例如,当 root 在 iSCSI 上时。因为这样 initrd 就需要评估位于 iSCSI 上的 root 分区了。</p>\n"
"<p><b>自动</b>用于当 iSCSI 服务启动时自动连接的 iSCSI 目标。</p>\n"
#. list of discovered targets
#: src/include/iscsi-client/helps.rb:142
-msgid ""
-"List of discovered targets. Start a new <b>Discovery</b> or <b>Connect</b> "
-"to any target."
+msgid "List of discovered targets. Start a new <b>Discovery</b> or <b>Connect</b> to any target."
msgstr "已发现的目标列表。可启动新<b>发现</b>或<b>连接</b>到任意目标。"
#: src/include/iscsi-client/helps.rb:145
@@ -526,9 +504,7 @@
#. check if not already connected
#: src/include/iscsi-client/widgets.rb:771
#: src/include/iscsi-client/widgets.rb:891
-msgid ""
-"The target with this TargetName is already connected. Make sure that "
-"multipathing is enabled to prevent data corruption."
+msgid "The target with this TargetName is already connected. Make sure that multipathing is enabled to prevent data corruption."
msgstr "已连接名称为此目标名称的目标。请确保启用了多路径以防止数据损坏。"
#: src/include/iscsi-client/widgets.rb:774
@@ -559,9 +535,7 @@
#. don't check interactively for packages (bnc#367300)
#. skip it during second stage or when create AY profile
#: src/modules/IscsiClient.rb:96
-msgid ""
-"<p>To configure the iSCSI initiator, the <b>%1</b> package must be installed."
-"</p>"
+msgid "<p>To configure the iSCSI initiator, the <b>%1</b> package must be installed.</p>"
msgstr "<p>必须安装 <b>%1</b> 软件包才能配置 iSCSI 发起端。</p>"
#: src/modules/IscsiClient.rb:99
Modified: trunk/yast/zh_CN/po/iscsi-lio-server.zh_CN.po
===================================================================
--- trunk/yast/zh_CN/po/iscsi-lio-server.zh_CN.po 2014-10-07 15:48:22 UTC (rev 89783)
+++ trunk/yast/zh_CN/po/iscsi-lio-server.zh_CN.po 2014-10-07 15:49:12 UTC (rev 89784)
@@ -8,7 +8,7 @@
msgstr ""
"Project-Id-Version: YaST (@memory@)\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-06-06 16:39+0200\n"
+"POT-Creation-Date: 2014-07-04 15:52+0200\n"
"PO-Revision-Date: 2014-06-11 12:55+0800\n"
"Last-Translator: 玛格丽特 · 苏
<li>Select <b>Include unknown security events</b> if you would like "
-#~ "to include events that are not rated with a severity number.</li> </ol>"
-#~ msgstr ""
-#~ "“安全事件通知”屏幕使您可以为安全事件设置电子邮件警报。在以下步骤中,指定发"
-#~ "送警报的频率、接收警报的接收人以及必须发送警报的安全事件的严重性。"
-#~ "<br><br><b>通知类型</b><br> <b>简要通知:</b>简要通知提供总系统事件的总"
-#~ "数,而不提供详细信息。<br>例如:<br> dhcp-101.up.wirex.com has had 10 "
-#~ "security events since Tue Oct 12 11:10:00 2004<br><br> <b>摘要通知:</b>摘"
-#~ "要通知显示所记录的 AppArmor 安全事件,并列出各自发生的次数,包括上次发生的"
-#~ "日期。<br>例如:<br> SubDomain: PERMITTING access to capability "
-#~ "'setgid' (httpd2-prefork(6347) profile /usr/sbin/httpd2-prefork active /"
-#~ "usr/sbin/httpd2-prefork) 2 times, the latest at Sat Oct 9 16:05:54 2004."
-#~ "<br><br> <b>冗长通知:</b>冗长通知显示未经修改记录的 AppArmor 安全事件。它"
-#~ "在每次事件发生时告知您并在详细日志中写入新的一行。这些安全事件包括事件发生"
-#~ "的日期和时间、应用程序设置存档允许访问和拒绝访问的时间以及被允许或拒绝的文"
-#~ "件访问权限的类型。冗长通知还报告 logprof 工具用于解释设置存档的一些讯息。"
-#~ "<br>例如:<br>Oct 9 15:40:31 SubDomain: PERMITTING r access to /etc/"
-#~ "apache2/httpd.conf (httpd2-prefork(6068) profile /usr/sbin/httpd2-prefork "
-#~ "active /usr/sbin/httpd2-prefork) <br><br> <ol> <li>对于要启用的每个通知类"
-#~ "型,都请选择所需的通知频率。例如,如果从下拉列表中选择 <b>1 天</b>,则将向"
-#~ "您发送安全事件的每天通知(如果发生安全事件)。</li> <br><br> <li>输入应接"
-#~ "收“简要”、“摘要”或“详细”通知的人的电子邮件地址。</li><br><br> <li>选择应发"
-#~ "送通知的最低<b>严重性级别</b>。当事件大于等于所选的严重性级别时,记录安全"
-#~ "事件和发送通知都按照时间间隔进行。如果时间间隔为 1 天,则通知将每天发送(如"
-#~ "果发生安全事件)。<br><br> <b>严重性级别:</b>从 1 到 10,10 是最严重的安全"
-#~ "事件。<b>severity.db</b> 文件定义潜在安全事件的严重性级别。严重性级别是由"
-#~ "不同安全事件的重要性定义的,如访问某些资源或拒绝某些服务。</li> <li>如果要"
-#~ "包含没有安全评级的事件,则选择<b>包含未知安全事件</b>。</li> </ol>"
+#~ msgid "The Security Event Notification screen enables you to setup email alerts for security events. In the following steps, specify how often alerts are sent, who receives the alert, and how severe the security event must be to send an alert. <br><br><b>Notification Types</b><br> <b>Terse Notification:</b> Terse notification summarizes the total number of system events without providing details. <br>For example:<br> dhcp-101.up.wirex.com has had 10 security events since Tue Oct 12 11:10:00 2004<br><br> <b>Summary Notification:</b> The Summary notification displays the logged AppArmor security events, and lists the number of individual occurrences, including the date of the last occurrence. <br>For example:<br> SubDomain: PERMITTING access to capability 'setgid' (httpd2-prefork(6347) profile /usr/sbin/httpd2-prefork active /usr/sbin/httpd2-prefork) 2 times, the latest at Sat Oct 9 16:05:54 2004.<br><br> <b>Verbose Notification:</b> The Verbose notification displays unmodified
, logged AppArmor security events. It tells you every time an event occurs and writes a new line in the Verbose log. These security events include the date and time the event occurred, when the application profile permits access as well as rejects access, and the type of file permission access that is permitted or rejected. Verbose Notification also reports several messages that the logprof tool uses to interpret profiles. <br>For example:<br> Oct 9 15:40:31 SubDomain: PERMITTING r access to /etc/apache2/httpd.conf (httpd2-prefork(6068) profile /usr/sbin/httpd2-prefork active /usr/sbin/httpd2-prefork)
<br><br> <ol> <li>Click <b>Filter By Date Range</b>. The fields become "
-#~ "active. <li>Enter the start and end dates that delineate the scope of "
-#~ "the report. <li>Enter other filtering parameters. See below for "
-#~ "definitions of parameters. </ol> The following definitions help you to "
-#~ "enter the filtering parameters in the Report Configuration Dialog: "
-#~ "<br><br> <b>Program Name Pattern:</b> When you enter a program name or "
-#~ "pattern that matches the name of the binary executable of the program of "
-#~ "interest, the report will display security events that have occurred for "
-#~ "a specific program.<br><br> <b>Profile Name Pattern:</b> When you enter "
-#~ "the name of the profile, the report will display the security events that "
-#~ "are generated for the specified profile. You can use this to see what is "
-#~ "being confined by a specific profile.<br><br> <b>PID Number:</b> Process "
-#~ "ID number is a number that uniquely identifies one specific process or "
-#~ "running program (this number is valid only during the lifetime of that "
-#~ "process).<br><br> <b>Severity Level:</b> Select the lowest severity "
-#~ "level for security events that you would like to be included in the "
-#~ "report. The selected severity level, and above, will be included in the "
-#~ "reports.<br><br> <b>Detail:</b> A source to which the profile has denied "
-#~ "access. This includes capabilities and files. You can use this field to "
-#~ "report the resources are not allowed to be accessed by profiles.<br><br> "
-#~ "<b>Mode:</b> The Mode is the permission that the profile grants to the "
-#~ "program or process to which it is applied. The options are: r (read) w "
-#~ "(write) l (link) x (execute)<br><br> <b>Access Type:</b> The access type "
-#~ "describes what is actually happening with the security event. The options "
-#~ "are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> "
-#~ "Enables you to export a CSV (comma separated values) or html file. The "
-#~ "CSV file separates pieces of data in the log entries with commas using a "
-#~ "standard data format for importing into table-oriented applications. You "
-#~ "can enter a pathname for your exported report by typing in the full "
-#~ "pathname in the field provided.</p>"
-#~ msgstr ""
-#~ "“报告配置”对话框使您能够过滤在以前屏幕中选择的存档报告。要按<b>日期范围"
-#~ "b>过滤:<br><br><ol> <li>请单击<b>按日期范围过滤</b>。该字段变为活动状态。"
-#~ "<li>输入描述报告范围的开始和结束日期。<li>输入其他过滤参数。参考以下的参数"
-#~ "定义。</ol>以下定义有助于您在“报告配置”对话框中输入过滤参数:<br><br> <b>"
-#~ "程序名称模式:</b> 当您输入的程序名称或模式与所涉及程序的二进制可执行文件"
-#~ "的名称相匹配时,报告将显示针对特定程序发生的安全性事件。<br><br> <b>设置存"
-#~ "档名称模式:</b>当您输入设置存档名称时,报告将显示针对指定设置存档生成的安"
-#~ "全性事件。由此您可以看到特定设置存档所限制的内容。<br><br><b>PID 号:</b> "
-#~ "进程 ID 号是一个编号,用来唯一标识某个特定进程或正在运行的程序(此编号仅在"
-#~ "该进程的有效期内有效)。<br><br> <b>严重性级别:</b>请为您要在报告中包含的"
-#~ "安全性事件选择最低的严重性级别。选定的严重性级别及更高级别将包含在报告中。"
-#~ "<br><br><b>细节:</b>设置存档已拒绝访问的源。这包含功能和文件。您可以使用"
-#~ "此字段来报告不允许设置存档访问的资源。<br><br><b>方式:</b>“方式”是设置存"
-#~ "档授予应用该设置存档的程序或进程的许可权限。其选项为:r(读)w(写)l(链"
-#~ "接)x(执行)<br><br> <b>访问类型:</b>访问类型描述了安全性事件真正发生的"
-#~ "内容。其选项为:允许、拒绝或审计。<br><br><b>CSV 或 HTML:</b>使您能够导"
-#~ "出 CSV(逗号分隔值)或 html 文件。CSV 文件使用标准数据格式,将日志条目中的"
-#~ "数据片段用逗号分隔开,以便于导入面向表的应用程序。您可以输入已导出报告的路"
-#~ "径名,方法是在提供的字段中输入它的完整路径名。"
+#~ msgid "<p>The Report Configuration dialog enables you to filter the archived report selected in the previous screen. To filter by <b>Date Range:</b><br><br> <ol> <li>Click <b>Filter By Date Range</b>. The fields become active. <li>Enter the start and end dates that delineate the scope of the report. <li>Enter other filtering parameters. See below for definitions of parameters. </ol> The following definitions help you to enter the filtering parameters in the Report Configuration Dialog: <br><br> <b>Program Name Pattern:</b> When you enter a program name or pattern that matches the name of the binary executable of the program of interest, the report will display security events that have occurred for a specific program.<br><br> <b>Profile Name Pattern:</b> When you enter the name of the profile, the report will display the security events that are generated for the specified profile. You can use this to see what is being confined by a specific profile.<br><br> <b>PID Number: