On Tue, 17 Dec 2024 at 22:20, Stephen Morris <[email protected]>
wrote:
> Hi,
> How does Tracer decide on what messages to display and what
> instructions to provide. For example, what does it look at to produce the
> following snippet of its output, especially when I ran "sudo akonadictl
> restart" and that command said Akonadi wasn't running? If it is restarting
> other associated applications then where are the messages about what it is
> restarting and whether or not it was successful?
>
> You should restart:
> * Some applications using:
> akonadictl restart
>
> * These applications manually:
> DiscoverNotifier
> akonadi_archivemail_agent
>
> sudo akonadictl restart
> Akonadi is not running.
>
First I'd review the man page:
DESCRIPTION
Tracer determines which applications use outdated files and prints
them. For special kind of
applications such as services or daemons, it suggests a standard
command to restart it. Detecting
whether file is outdated or not is based on a simple idea. If
application has loaded in memory any ver‐
sion of a file which is provided by any package updated since system
was booted up, tracer consider
this application as outdated.
If that's 100% the case, then it's looking at fairly crude deltas in order
to figure out what needs restarting. And restarting a service doesn't
change tracer's output. Since it's calculating the delta between last boot
and packages updated.
Then anecdotally, I've just updated a system, restarted a service tracer
has identified (as you have), tracer still tells me that it needs
restarting because the calculated delta hasn't changed, despite the service
being restarted?
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue