Swif’s Linux Software Update Policy is designed to automate the process of keeping your Linux devices up to date. Because Linux distributions vary widely and do not offer a single, unified API (unlike macOS or Windows), Swif implements its own MDM features on each distro. This means the way automatic updates, repositories, and system settings appear can differ from your usual experience on a particular Linux system.
Below, we’ll clarify key points to help you understand and troubleshoot how updates are handled under Swif’s management.
1. Why Swif Creates a New Repository List
Swif may create or manage additional repository lists inside sources.list.d/. Swif creates additional repository lists here in 3 scenarios:
If Software Update Policy configures
ReposIf there is a repo of an application in the package settings (for example, Chrome).
Swif can add its service repos for the auto-update mechanism.
Important: Swif does not always modify the main sources.list. Instead, it places its own repository list in sources.list.d to avoid conflicts and ensure MDM-managed updates remain separate and trackable.
2. How “Automatic Update” Works
When you select Automatic Update in the Linux Software Update Policy, Swif instructs the device to update at predetermined intervals (usually 2–3 times a day). Specifically, it runs standard commands (or their equivalents on your distribution) such as:
apt update && apt upgrade
(for Debian/Ubuntu-based distros) or the relevant package-manager commands (e.g., dnf, yum, zypper, etc.) on other distributions.
Key Points:
Swif is using the system package manager with the Swif agent.
This process is independent of the device’s built-in settings panel. Hence, your system might still show “Automatic updates: Off” in native settings, because Swif manages updates outside of the OS’s default toggles.
If your organization wants certain repositories included, you can add them in Swif’s “Repos” section for the Linux Software Update Policy.
3. Adding Custom Repositories (Repos Section)
Sometimes you may need additional repositories (e.g., for internal tools, specialized software, or particular package versions). Swif’s Linux Software Update Policy includes a Repos section so you can specify your own repos:
In the Swif admin console, go to Device Management > Policies > Linux Software Update Policy.
Find the Repos field or section and add the repo’s details (e.g., the GPG key URL and the repository address).
Save the policy and deploy.
Swif will create or modify the relevant .list file under sources.list.d, ensuring your devices download packages from those repositories during the next scheduled update cycle.
4. Common Questions
Q1: Why does my system settings panel say “Automatic Updates Off” while Swif is updating packages?
A1: Linux distributions generally don’t offer a unified MDM API. Swif manages updates through its own mechanisms using the system’s package manager. The native distro settings panel can’t “see” or control Swif’s MDM logic, so it may display “Off” even though updates are running.
Q2: Does Swif only add repos if they’re missing, or might it create new lists?
A2: Swif can create new .list files within sources.list.d to ensure it can manage them separately. This allows better control without altering the default distro repository setup. In many cases, it checks if the needed repo already exists; if not, it adds a new one.
Q3: How often does Swif’s Automatic Update run?
A3: By default, it runs 2–3 times a day, although exact frequency can depend on your Swif policy configuration. Each run triggers package-manager commands like apt update && apt upgrade (or the equivalent for your distribution).
Q4: Can I rely on only the default repositories for updates?
A4: Absolutely. If you don’t need extra software sources, simply refrain from adding custom repos in the policy. Swif will still automatically use the distro’s default repositories for updates.
Q5: Is it safe to manually remove or edit the .list file Swif creates?
A5: We strongly recommend using Swif’s policy settings to manage repositories. Manual changes might conflict with Swif’s automation and could lead to unexpected behavior or errors.
5. Troubleshooting & Best Practices
Check Logs: If an update fails, consult the device’s package manager logs (e.g.,
/var/log/apt/history.logor/var/log/dnf.log) and Swif’s device logs in the admin console.Avoid Manual Interference: Let Swif handle repo creation and updates. If you need changes, do it through the Swif console.
Consistency Across Distros: Because each distro can behave differently, ensure your repos and packages are compatible. Test on a small group of devices before rolling out widely.
Communication: If end-users or IT staff see “Automatic Updates: Off” in their system settings, inform them that updates are handled by Swif and not the built-in OS feature.
Summary
Swif’s Linux Software Update Policy is purpose-built to manage updates for a wide range of distributions. By creating and managing its own repository list files, Swif ensures consistency across devices without disrupting native distro files. Although you may see discrepancies in system settings (“Automatic Updates Off”), rest assured Swif is handling updates behind the scenes, typically running 2–3 times daily to keep your packages current and secure.
For additional support or details on advanced configurations, please reach out to Swif Support or visit the Swif Help Center.