On Tue, 2024-12-17 at 22:47 +0000, Will McDonald wrote: > On Tue, 17 Dec 2024 at 22:20, Stephen Morris <steve.morris.au@xxxxxxxxx> > 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? It definitely does change tracer's output. I use this on a daily basis. Any time I restart something and check again with 'tracer' it notices and doesn't flag the service or app. I suspect a documentation bug. It doesn't seem to me that it's checking against boot time but against the last time the service or app was updated, which makes more sense. poc -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
