Exit Zen
2357
include/global_settings.php:1148
English
Show business hours
31/190 · 19
2497
include/global_settings.php:1760 • user_domains.php:423
English
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.
0/5920 · 592
2626
include/global_settings.php:2296
English
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.
0/7550 · 755
2870
lib/boost.php:63 • utilities.php:2762
English
%s MBytes
7/100 · 9
3067
lib/html.php:616
English
Current Page: %s
0/160 · 16
3292
lib/html_reports.php:1624
English
Graph: %s
38/100 · 9
3294
lib/html_reports.php:1637
English
Device: %s
13/100 · 10
3298
lib/html_reports.php:1691
English
Tree: %s
12/100 · 8
3299
lib/html_reports.php:1699
English
, Device: %s
13/120 · 12
3619
lib/ldap.php:318
English
Unable to Connect to Server (%s)
31/320 · 32
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.
0/7640 · 764
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.
0/5380 · 538
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.
0/4050 · 405
4128
templates_import.php:321
English
Met: %d
12/100 · 7
4129
templates_import.php:325
English
Unmet: %d
13/100 · 9
The translation has come to an end.