2. Cacti
3. core
4. Japanese
5. Browse

9 / 11

/ 11

Not translated strings

• 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	Japanese
	Proceed with Action
	Return to previous page
	Cacti regular expressions are limited to 50 characters only for security reasons.
	Cacti regular expressions can not includes the semi-color character.
	The specificed value appears to be different in the running config versus the INI file.
	IPv6 support seems to be missing!
	IPv6 support appears to be missing!
	NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure
	If this number is negative, reduce the innodb_buffer_pool_size until the join_buffer_size turns positive, but allocate approximately from between 25%-50% of memory to the innodb_buffer_pool_size if the database is hosted on the Cacti server, or upto 80% of the systems memory if the database is separate from the Cacti web server. However, try to not go below the default of 262,144. 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 database is hosted on the Cacti web server and less if you intend to have very large RRDfiles or hundreds of thousands to millions long term.
	If this number is negative, reduce the innodb_buffer_pool_size until the sort_buffer_size turns positive, but allocate approximately from between 25%-50% of memory to the innodb_buffer_pool_size if the database is hosted on the Cacti server, or upto 80% of the system memory if the database is separate from the Cacti web server. However, try to not go below the default setting of 2,097,152. A sort buffer performs sorts for some queries using ORDER BY or GROUP BY. Configuring sort_buffer_size decides how much memory will be allocated for sort queries. The sort_buffer_size may need to be adjusted from the default if the workload requires a significant number of sort queries. The sort_buffer_size is defined on a per-session variable. Use the same equation as that of the join_buffer_size to determine the per connection possible memory.
	Key Generation Required to Use Plugin
	Package Key Information Not Found
	In order to use this Plugin, you must first run the <b><i class="deviceUp">genkey.php</i></b> script in the plugin directory. Once that is complete, you will have a public and private key used to sign your packages.
	You have not Trusted this Package Author. If you wish to import, check the Automatically Trust Author checkbox
	The Package %s Import Failed
	See the cacti.log for more information. It could be that you had either an API Key error or the package was tamered with, or the location is not available.
	See the cacti.log for more information. It could be that you had either an API Key error or the package was tamered with, or the location is not available
	The package download or validation failed
	The XML files appears to be invalid. Please contact the package author
	Check the package repository file for files that should exist and find the one that is missing