{"version":"2.1.229","anchor":"background-roster-and-dispatch-files-handle-symlinks-and-unr","canonical_anchor":"background-roster-and-dispatch-files-handle-symlinks-and-unr","heading":"Background roster and dispatch files handle symlinks and unreadable files explicitly","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/background-roster-and-dispatch-files-handle-symlinks-and-unr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Background roster and dispatch files handle symlinks and unreadable files explicitly\n\nBackground task files that are symlinks or unreadable are quarantined or skipped instead of trusted.\n\n**What**\n\nThe background task roster file and the dispatch files it works with are now inspected before use. Symlinks and anything that is not a regular file are quarantined or removed instead of read, and a file that cannot be inspected produces a clear skip message rather than being treated as missing.\n\n**Details**\n\n- Message on skip: `bg roster.json update skipped: the file could not be inspected`\n- Read errors that mean the filesystem refused (ENXIO, EFBIG, ELOOP, ENAMETOOLONG) take their own path rather than being lumped in with \"not found\"\n\n**Evidence**\n\n`bg roster.json update skipped: the file could not be inspected`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}