English Latvian
Click 'Continue' to delete the following CDEF. Noklikšķiniet uz "Turpināt", lai dzēstu šo CDEF vienumu.
Click 'Continue' to delete the following Color Template Noklikšķiniet uz "Turpināt", lai dzēstu šādu krāsu veidnes krāsu.
Click 'Continue' to Delete the following Data Query. Noklikšķiniet uz "Turpināt", lai dzēstu šo datu vaicājumu diagrammas asociāciju.
Click 'Continue' to delete the following Data Source Profile Noklikšķiniet uz "Turpināt", lai dzēstu šo datu avota profilu RRA.
Click 'Continue' to delete the following Data Source Noklikšķiniet uz "Turpināt", lai dzēstu šo datu avota profilu RRA.
Click 'Continue' to delete the following VDEF. Noklikšķiniet uz "Turpināt", lai dzēstu tālāk norādītos VDEF.
Delete CDEF Dzēst CDEF vienumu
Delete Color Template Dzēst krāsu veidni(-es)
Delete Data Source Profile Dzēst datu avota profila vienumu
Delete VDEF Dzēst VDEF vienumu
Disable Data Source Atspējot datu avotu.
Enable Data Source Iespējot datu avotu.
Met: %d Izpildīts
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.
Use a separate subfolder for each hosts RRD files. The naming of the RRDfiles will be one of the following:<br><ul><li>&lt;path_cacti&gt;/rra/host_id/local_data_id.rrd,</li><li>&lt;path_cacti&gt;/rra/device_id/data_query_id/local_data_id.rrd,</li><li>&lt;path_cacti&gt;/rra/device_hash/device_id/local_data_id.rrd,</li><li>&lt;path_cacti&gt;/rra/device_hash/device_id/data_query_id/local_data_id.rrd.</li></ul><br>You can make this change after install by running the CLI script <b>structure_rra_paths.php</b> after you make the change. NOTE: If you change Max Directories value to decrease the number of directories, or if you change the Directory Pattern, empty directories will not be pruned after you rerun the <b>structure_rra_paths.php</b> script.
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.