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

19 / 20

/ 20

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	Latvian
	The ID of the Task which is often times the LSF clusterid or the License Service ID, but can be other metrics as well.
	The Process runtime or times since last heartbeat.
	The background process timeout in seconds when a Cacti process. Otherwise controlled by the individual plugins.
	Time the background process started for a Cacti process. The start time may or may not be supported for various plugins.
	Time the process last registered its status to the status tables.
	No Cacti or Plugin Background Processes Found
	Worst 20 failed/total polls ratio
	Failed/Total polls
	Reduce MySQL/MariaDB Memory to less than 80% of System Memory. Preserve additional Cache Memory for RRDfiles if the Database is on the same system as the RRDfiles. See Core and Client Totals below for explanation of calculation method.
	The Template Import Succeeded.
	See the cacti.log for more information, and review the XML file for proper syntax. The error details are shown below.<br><br><b>Errors:</b><br>%s
	The Template XML file "%s" validation failed
	Import Files [ If Files are missing, locate and install before using ]
	Import Templates [ None selected imports all, Check to import selectively ]
	Unmet: %d
	Some CDEF Items will not import due to an export error! Contact Template provider for an updated export.
	< 1 Month Ago
	> 1 Month Ago
	The "Distinguished Name" syntax, applicable for both OpenLDAP and Windows AD configurations, offers flexibility in defining user identity. For OpenLDAP, the format follows this structure: <i>"uid=&lt;username&gt;,ou=people,dc=domain,dc=local"</i>. Windows AD provides an alternative syntax: <i>"&lt;username&gt;@win2kdomain.local"</i>, commonly known as "userPrincipalName (UPN)". In this context, "&lt;username&gt;" represents the specific username provided during the login prompt. This is particularly pertinent when operating in "No Searching" mode, or "Require Group Membership" enabled.
	This refers to the specific attribute within the LDAP directory that holds the usernames of group members. It is crucial to ensure that the attribute value aligns with the configuration specified in the "Distinguished Name" or that the actual attribute value is searchable using the settings outlined in the "Distinguished Name".