anchor.diff:  ==== Configuration
   
   To communicate with the SOTA Client over unix domain sockets, `socket = true` must be defined in the `[gateway]` section of the config file. Additionally, the names of the two sockets are configurable in the link:#__network[[network]] section.
  +
  +The SOTA Client will create the commands socket, but the software loading manager must create the events socket. Note that it must be readable and writable by root, and be at the location configured in `sota.toml`.
   
   ==== DownloadComplete
   
  
positive.code: :icons: font
  :toc: left
  :toclevels: 3
  
  == Starting the SOTA client
  
  
negative.code: <4> The frequency, in seconds, with which the SOTA client should poll the server for updates.
  <5> The location SOTA Client should use for temporary package storage until they are processed by the software loading manager.
  <6> The software loading manager backend to use. Possible values are `deb`, `rpm`, and `off`. If an external software loading manager is in use, this should be set to `off`.
  <7> The certificate authorities SOTA Client trusts. The recommended defaults are taken from Mozilla Servo, and the default certificates file can be downloaded from https://raw.githubusercontent.com/advancedtelematic/rvi_sota_client/master/run/sota_certificates[the SOTA client repo]. You may also use your own CA file or the operating system's default trusted certificates file, but ATS recommends using the provided certificate file.
  
  === [network]
  
  