On 18/12/24 10:29, Patrick O'Callaghan wrote:
On Tue, 2024-12-17 at 22:47 +0000, Will McDonald wrote:
On Tue, 17 Dec 2024 at 22:20, Stephen Morris<steve.morris...@gmail.com>
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.

Yes, but why would it suggest restarting an applications that are possibly not actually running, as the command shows akonadi wasn't running, so why produce a message that it needs restarting?

Just on that front and slightly off topic to this question, I've had tracer tell me I need to manually restart Plasma Shell, how does one actually do that without rebooting the system or without the restart of that forcing a reboot?

regards,
Steve


poc

Attachment: OpenPGP_0x1EBE7C07B0F7242C.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

-- 
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to