![]() ![]() Read-only:future - Commands that are likely to result in running other commands which will require the latest metadata. Read-only:present - Commands that are balanced between past and future. yum history info (if history needs to lookup anything about a previous transaction, then by definition the remote package was available in the past). Read-only:past - Commands that only care about past information are filtered from metadata expiring. Never - Nothing is filtered, always obey metadata_expire. from “I’m about to install/upgrade, so this better be current” to “Anything that’s available is good enough”. Each yum command can specify that it requires a certain level of timeliness quality from the remote repos. Controlling how Ansible behaves: precedence rulesįilter the metadata_expire time, allowing a trade of speed for accuracy if a command doesn’t require it.Collections in the Theforeman Namespace.Collections in the T_systems_mms Namespace.Collections in the Purestorage Namespace.Collections in the Openvswitch Namespace.Collections in the Netapp_eseries Namespace.Collections in the Kubernetes Namespace.Collections in the Junipernetworks Namespace.Collections in the F5networks Namespace.Collections in the Containers Namespace.Collections in the Cloudscale_ch Namespace.Collections in the Chocolatey Namespace.Collections in the Check_point Namespace.Virtualization and Containerization Guides.Protecting sensitive data with Ansible vault. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |