Scanning Engine v2 - Module - rsync¶

Overview¶

Targeting¶

Configuration¶

Only the publicly-available configuration keys that can be set in a job's module invocations will be described below. Additional configuration keys may exist, but not be shown here because they are restricted to specific users or because they are permanently set as a static value. If no keys have (required) after their names then invocations of this module need not contain a config key.

Named Keys¶

`debug`¶

Run module with a debugging configuration.

Type: boolean

`full-mode`¶

Attempt to connect to all modules.

Type: boolean

`read-timeout`¶

Timeout for socket reads, in seconds.

Type: integer
Default: 5

Schemas¶

The schema for the body object of all results generated with .task.module_name equal to rsync can be found here. The schema for results is available both in standalone and bundled form.

Examples¶

These are examples of the .body object for results with .task.module_name equal to rsync.

Live Host¶

This example was generated with a live host on the internet.

{
  "status": "protected",
  "version": "31.0",
  "banner": "",
  "modules": [
    {
      "module": "homes",
      "status": "@RSYNCD: AUTHREQD"
    },
    {
      "module": "music",
      "status": "@RSYNCD: AUTHREQD"
    },
    {
      "module": "NetBackup",
      "status": "@RSYNCD: AUTHREQD"
    },
    {
      "module": "NoSync",
      "status": "@RSYNCD: AUTHREQD"
    },
    {
      "module": "photo",
      "status": "@RSYNCD: AUTHREQD"
    },
    {
      "module": "svn",
      "status": "@RSYNCD: AUTHREQD"
    },
    {
      "module": "tmp",
      "status": "@RSYNCD: AUTHREQD"
    },
    {
      "module": "video",
      "status": "@RSYNCD: AUTHREQD"
    },
    {
      "module": "web",
      "status": "@RSYNCD: AUTHREQD"
    },
    {
      "module": "home",
      "status": "@RSYNCD: AUTHREQD"
    }
  ]
}

Changelog¶

v1.0.0 (2025-07-08)¶

Initial release of versioning for each module. All modules are being tagged with version number 1.0.0. Going forward:
Major version should be changed when there are changes that impact consumers or clients of the modules.
Minor version should be changed when there are additions which enrich or enhance the module but shouldn't affect consumers or clients.
Patch version should be changed when there are bugfixes.