2. Cacti
3. core (v1.2.x)
4. Chinese (Traditional)
5. Browse

23 / 27

/ 27

Translated strings with any failing checks

• Not translated strings • state:empty
• Strings needing action • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with labels • has:label
• Strings with context • has:context
• Strings needing action without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Translated string
• Age of string
• Number of words
• Number of comments
• Number of failing checks
• Key

	English	Chinese (Traditional)
	The number of rows for Cacti RRA id '%s' is incorrect. The number of rows are '%s' but should be '%s'	Cacti RRA id'％s'的行數應為'％s'
	The RRA '%s' missing in the existing Cacti RRDfile	RRD文件中缺少RRA'％s'
	RRA '%s' missing in Cacti definition	Cacti定義中缺少RRA'％s'
	Round Robin Archive	Round Robin Archive
	Cur Row	Cur Row
	rename %s to %s	將％s重命名為％s
	ERROR while writing XML file: %s	編寫XML文件時出錯：％s
	ERROR: RRDfile %s not writeable	錯誤：RRDfile％s不可寫
	RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) removed from RRD file	從RRD文件中刪除RRA（CF =％s，ROWS =％d，PDP_PER_ROW =％d，XFF =％1.2f）
	RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) adding to RRD file	RRA（CF =％s，ROWS =％d，PDP_PER_ROW =％d，XFF =％1.2f）添加到RRD文件
	Website does not have write access to %s, may be unable to create/update RRDs	網站沒有％s的寫入權限，可能無法創建/更新RRD
	Graph Not created for %s due to bad data	圖形創建
	It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3.	建議您在大於5.1的任何％s版本中啟用InnoDB。
	It is recommended that you enable InnoDB in any %s version greater than 5.1.	建議您在大於5.1的任何％s版本中啟用InnoDB。
	Depending on the number of logins and use of spine data collector, %s will need many connections. The calculation for spine is: total_connections = total_processes * (total_threads + script_servers + 1), then you must leave headroom for user connections, which will change depending on the number of concurrent login accounts.	根據登錄次數和使用脊椎數據收集器，％s將需要許多連接。 spine的計算是：total_connections = total_processes *（total_threads + script_servers + 1），然後您必須為用戶連接留出空間，這將根據並發登錄帳戶的數量而變化。
	When using InnoDB storage it is important to keep your table spaces separate. This makes managing the tables simpler for long time users of %s. If you are running with this currently off, you can migrate to the per file storage by enabling the feature, and then running an alter statement on all InnoDB tables.	使用InnoDB存儲時，將表空間分開是很重要的。這使得對於％s的長時間用戶來說，管理表更簡單。如果您當前正在運行此服務，則可以通過啟用該功能，然後在所有InnoDB表上運行alter語句來遷移到每個文件存儲。
	Setting this value to 2 means that you will flush all transactions every second rather than at commit. This allows %s to perform writing less often.	將此值設置為2意味著您將每秒刷新所有事務而不是提交。這允許％s更少地執行寫入。
	As of %s %s, the you can control how often %s flushes transactions to disk. The default is 1 second, but in high I/O systems setting to a value greater than 1 can allow disk I/O to be more sequential	從％s％s開始，您可以控制％s將事務刷新到磁盤的頻率。默認值為1秒，但在高I / O系統中設置為大於1的值可以允許磁盤I / O更順序
	%s will divide the innodb_buffer_pool into memory regions to improve performance for versions of MariaDB less than 10.5. The max value is 64, but should not exceed more than the number of CPU cores/threads. When your innodb_buffer_pool is less than 1GB, you should use the pool size divided by 128MB. Continue to use this equation up to the max the number of CPU cores or 64.	％s會將innodb_buffer_pool劃分為內存區域以提高性能。最大值為64.當你的innodb_buffer_pool小於1GB時，你應該使用池大小除以128MB。繼續使用此公式，最大值為64。
	%s will divide the innodb_buffer_pool into memory regions to improve performance for versions of MySQL upto and including MySQL 8.0. The max value is 64, but should not exceed more than the number of CPU cores/threads. When your innodb_buffer_pool is less than 1GB, you should use the pool size divided by 128MB. Continue to use this equation up to the max of the number of CPU cores or 64.	％s會將innodb_buffer_pool劃分為內存區域以提高性能。最大值為64.當你的innodb_buffer_pool小於1GB時，你應該使用池大小除以128MB。繼續使用此公式，最大值為64。