checkservices does not offer to restart user services

[curiosityseeker]

See the detailed discussion on Antiz96/arch-update#410.

While tracer and longoverdue output the user services that should be restarted after an update, checkservices does not, even when started with the -u option.

Sidenote: the explanations in checkservices -h are a bit ambiguous, IMO.

usage checkservices [options]
description: check for updated files in a service
options:
  -h: this help
  -a/-A: auto confirmation (or not) (default: 0)
  -l/-L: call (or not) systemd daemon-(reload|reexec) (default: 1)
  -f/-F: display (or not) failed services before quit (default: 1)
  -p/-P: call (or not) pacdiff before act (default: 1)
  -r/-R: restart (or not) services with updated files (default: 1)
  -s/-S: display (or not) status of restarted service (default: 1)
  -u/-U: act (or not) on services in users slice (default: 0)
  -m/-M: act (or not) on services in machine slice (default: 0)
  -z/-Z: serialize (or not) action (default: 0)
  -i 'service_name'.service: ignore a specific service (can be used multiple times)

Does, e.g., -u/-U: act (or not) on services in users slice (default: 0) mean that using -u or -U lets checkservices act on users slice, or does it mean that -u lets it act on users slice and -U does not? I suggest that this should be clarified.

[Antiz96]

Hi,

Thanks for the report! 🤗

The first option acts on the concerned scope (=1), the second does not (=0). So in that case, -u is supposed to check for user services, while -U doesn't (and is the default).

[curiosityseeker]

Thanks, that's what I thought. But I still think that it should be rephrased to make it clearer.

[Antiz96]

Fair enough, I'll see if I can come up with something less confusing.