2. Cacti
3. core (v1.2.x)
4. Chinese (Traditional Han script)
5. Zen

3708 lib/template.php:1504
	English Attempting to Create Graph from Removed Graph Template
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 嘗試從已刪除的圖形模板創建圖形 15/540 · 54 Needs editing
3709 lib/template.php:2135 • lib/template.php:2169
	English Created: %s
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 已建立%s 5/110 · 11 Needs editing
3710 lib/template.php:2151 • lib/template.php:2180
	English ERROR: Whitelist Validation Failed. Check Data Input Method
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 錯誤：白名單驗證失敗。檢查數據輸入方法 19/590 · 59 Needs editing
3711 lib/template.php:2159
	English Graph Not created for %s due to bad data
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 圖形創建 4/400 · 40 Needs editing
3712 lib/template.php:2188
	English NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 0/920 · 92 Needs editing
3713 lib/utility.php:954
	English MySQL 5.6+ and MariaDB 10.0+ are great releases, and are very good versions to choose. Make sure you run the very latest release though which fixes a long standing low level networking issue that was causing spine many issues with reliability.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — MySQL 5.6+和MariaDB 10.0+是很棒的版本，是非常好的版本。確保你運行最新的版本，雖然它解決了一個長期存在的低級別網絡問題，這個問題導致脊柱出現許多可靠性問題。 89/2430 · 243 Needs editing
3714 lib/utility.php:966
	English It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 建議您在大於5.1的任何％s版本中啟用InnoDB。 26/870 · 87 Needs editing
3715 lib/utility.php:979 • lib/utility.php:1016
	English When using Cacti with languages other than English, it is important to use the utf8mb4_unicode_ci collation type as some characters take more than a single byte.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 將Cacti與英語以外的語言一起使用時，使用utf8mb4_unicode_ci校對類型非常重要，因為某些字符需要多個字節。 62/1610 · 161 Needs editing
3716 lib/utility.php:985 • lib/utility.php:991 • lib/utility.php:1022 • lib/utility.php:1028
	English When using Cacti with languages other than English, it is important to use the utf8mb4 character set as some characters take more than a single byte.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 將Cacti與英語以外的語言一起使用時，使用utf8mb4字符集非常重要，因為某些字符需要多個字節。 50/1490 · 149 Needs editing
3717 lib/utility.php:1004
	English It is recommended that you enable InnoDB in any %s version greater than 5.1.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 建議您在大於5.1的任何％s版本中啟用InnoDB。 26/760 · 76 Needs editing
3718 lib/utility.php:1037
	English 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.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 根據登錄次數和使用脊椎數據收集器，％s將需要許多連接。 spine的計算是：total_connections = total_processes *（total_threads + script_servers + 1），然後您必須為用戶連接留出空間，這將根據並發登錄帳戶的數量而變化。 144/3270 · 327 Needs editing
3719 lib/utility.php:1042
	English Keeping the table cache larger means less file open/close operations when using innodb_file_per_table.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 使用innodb_file_per_table時，保持表緩存更大意味著更少的文件打開/關閉操作。 48/1020 · 102 Needs editing
3720 lib/utility.php:1047
	English With Remote polling capabilities, large amounts of data will be synced from the main server to the remote pollers. Therefore, keep this value at or above 16M.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 使用遠程輪詢功能，大量數據將從主服務器同步到遠程輪詢器。因此，請將此值保持在16M或以上。 45/1590 · 159 Needs editing
3721 lib/utility.php:1053
	English If using the Cacti Performance Booster and choosing a memory storage engine, you have to be careful to flush your Performance Booster buffer before the system runs out of memory table space. This is done two ways, first reducing the size of your output column to just the right size. This column is in the tables poller_output, and poller_output_boost. The second thing you can do is allocate more memory to memory tables. We have arbitrarily chosen a recommended value of 10%% of system memory, but if you are using SSD disk drives, or have a smaller system, you may ignore this recommendation or choose a different storage engine. You may see the expected consumption of the Performance Booster tables under Console -> System Utilities -> View Boost Status.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 如果使用Cacti Performance Booster並選擇內存存儲引擎，則必須小心在系統內存表空間耗盡之前刷新Performance Booster緩衝區。這有兩種方法，首先將輸出列的大小減小到恰當的大小。此列位於表poller_output和poller_output_boost中。您可以做的第二件事是為內存表分配更多內存。我們已經任意選擇了10 %%系統內存的推薦值，但如果您使用的是SSD磁盤驅動器，或者係統較小，則可以忽略此建議或選擇其他存儲引擎。您可能會在Console - > System Utilities - > View Boost Status下看到Performance Booster表的預期消耗。 324/7640 · 764 Needs editing
3722 lib/utility.php:1059
	English When executing subqueries, having a larger temporary table size, keep those temporary tables in memory.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 執行子查詢時，臨時表大小較大時，請將這些臨時表保留在內存中。 30/1030 · 103 Needs editing
3723 lib/utility.php:1065 • lib/utility.php:1071
	English When performing joins, if they are below this size, they will be kept in memory and never written to a temporary file. As this is a per connection memory allocation, care must be taken not to increase it too high. The sum of the join_buffer_size + sort_buffer_size + read_buffer_size + read_rnd_buffer_size + thread_stack + binlog_cache_size + Core MySQL/MariaDB memory should be below 80%. If the recommendation is negative, you must decrease this and or the sort_buffer_size until the recommendation fits within the allowable memory.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 0/5380 · 538 Needs editing
3724 lib/utility.php:1077
	English 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.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 使用InnoDB存儲時，將表空間分開是很重要的。這使得對於％s的長時間用戶來說，管理表更簡單。如果您當前正在運行此服務，則可以通過啟用該功能，然後在所有InnoDB表上運行alter語句來遷移到每個文件存儲。 104/3120 · 312 Needs editing
3725 lib/utility.php:1083
	English When using innodb_file_per_table, it is important to set the innodb_file_format to Barracuda. This setting will allow longer indexes important for certain Cacti tables.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 使用innodb_file_per_table時，將innodb_file_format設置為Barracuda非常重要。此設置將允許更長的索引對某些Cacti表很重要。 85/1690 · 169 Needs editing
3726 lib/utility.php:1089
	English If your tables have very large indexes, you must operate with the Barracuda innodb_file_format and the innodb_large_prefix equal to 1. Failure to do this may result in plugins that can not properly create tables.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 如果表的索引很大，則必須使用梭子魚的innodb_file_format和innodb_large_prefix等於1的操作。否則可能導致插件無法正確創建表。 79/2130 · 213 Needs editing
3727 lib/utility.php:1095
	English InnoDB will hold as much tables and indexes in system memory as is possible. Therefore, you should make the innodb_buffer_pool large enough to hold as much of the tables and index in memory. Checking the size of the /var/lib/mysql/cacti directory will help in determining this value. We are recommending 25%% of your systems total memory, but your requirements will vary depending on your systems size.
	Chinese (Traditional Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — InnoDB將盡可能多地保存系統內存中的表和索引。因此，你應該使innodb_buffer_pool足夠大，以便在內存中保存盡可能多的表和索引。檢查/ var / lib / mysql / cacti目錄的大小將有助於確定此值。我們建議您的系統總內存佔25 %%，但您的要求會因係統大小而異。 147/4050 · 405 Needs editing