|
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.
|
|
|
Use a separate subfolder for each hosts RRD files. The naming of the RRDfiles will be one of the following:<br><ul><li><path_cacti>/rra/host_id/local_data_id.rrd,</li><li><path_cacti>/rra/device_id/data_query_id/local_data_id.rrd,</li><li><path_cacti>/rra/device_hash/device_id/local_data_id.rrd,</li><li><path_cacti>/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.
|
|
|
%s will divide the innodb_buffer_pool into memory regions to improve performance for versions of MariaDB less than 10.5. The max value is 64, but should not exceed more than the number of CPU cores/threads. When your innodb_buffer_pool is less than 1GB, you should use the pool size divided by 128MB. Continue to use this equation up to the max the number of CPU cores or 64.
|
|
|
%s will divide the innodb_buffer_pool into memory regions to improve performance for versions of MySQL upto and including MySQL 8.0. The max value is 64, but should not exceed more than the number of CPU cores/threads. When your innodb_buffer_pool is less than 1GB, you should use the pool size divided by 128MB. Continue to use this equation up to the max of the number of CPU cores or 64.
|
|
|
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=<username>,ou=people,dc=domain,dc=local"</i>. Windows AD provides an alternative syntax: <i>"<username>@win2kdomain.local"</i>, commonly known as "userPrincipalName (UPN)". In this context, "<username>" represents the specific username provided during the login prompt. This is particularly pertinent when operating in "No Searching" mode, or "Require Group Membership" enabled.
|
|
|
Operator.
|
- オペレーター - タンク
|
|
- Admin Filter active
|
- 管理フィルタがアクティブ
|
|
- Admin view
|
- 管理者ビュー
|
|
- Admin Unfiltered
|
- 管理者フィルタなし
|
|
Use --alt-autoscale-max (accepting a lower limit)
|
--alt-autoscale-maxを使用します（下限を受け入れます）
|
|
Use --alt-autoscale-min (accepting an upper limit)
|
--alt-autoscale-minを使用してください（上限を受け入れます）
|
|
Use --alt-autoscale (ignoring given limits)
|
--alt-autoscaleを使う（与えられた制限を無視する）
|
|
Use --alt-autoscale (accepting both limits, RRDtool default)
|
--alt-autoscaleを使用します（両方の制限を受け入れます、RRDtoolのデフォルト）。
|
|
T
|
・
|
|
, Graph Template: %s
|
,グラフテンプレート: %s
|
|
, Using RegEx: "%s"
|
、正規表現の使用： "%s"
|
|
. This is limited by the php setting 'max_input_vars', currently:
|
。これはphp設定'max_input_vars'によって制限されています。現在：
|
|
Executing SNMP walk for list of indexes @ '%s' Index Count: %s
|
'{ 0 }'インデックスカウントでインデックスリストのSNMPウォークを実行中: %s
|
|
Filtering list of indexes @ '%s' Index Count: %s
|
'{ 0 }'インデックス数でインデックスのリストをフィルタリングしています：{ 1}
|
|
List of indexes filtered by value @ '%s' Index Count: %s
|
'{ 0 }'インデックス数でフィルタリングされたインデックスのリスト: %s
|
