unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ben Sturmfels via <help-guix@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: Gnome Tracker (tracker-miner-fs-3) behaving badly
Date: Thu, 18 Aug 2022 11:56:48 +1000	[thread overview]
Message-ID: <87h72agvee.fsf@sturm.com.au> (raw)
In-Reply-To: <1A60F252-F243-49C3-8714-DCE0320C0844@tobias.gr>



Ben Sturmfels

Sturm Software Engineering
www.sturm.com.au
+61 3 9024 2467

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> Tracker logging every file it sees wouldn't be a good idea: apart from the wasted space, you'd be adding even more I/O load to the mix...
>
> Try stracing (guix install strace) tracker's PID(s) instead.  It will generate more output than you need, but file names should be obvious, and you can use grep to further filter the output.

Thanks Tobias, I'll give strace a shot. Regarding th logging - I'm not
entirely convinced that this would be a space/performance issue for most
use-cases, such as this personal/work laptop with email, code, photos
and media. I wouldn't expect to be generating new files or modifying
existing files at such a rate that the logging would create a problem,
and log rotation would take care of the wasted space eventually.

Regards,
Ben


  reply	other threads:[~2022-08-18  2:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  0:50 Gnome Tracker (tracker-miner-fs-3) behaving badly Ben Sturmfels via
2022-08-18  1:49 ` Tobias Geerinckx-Rice
2022-08-18  1:56   ` Ben Sturmfels via [this message]
2022-08-18  9:08 ` Ekaitz Zarraga
2022-08-18 18:43   ` indieterminacy
2022-08-18 23:17     ` Ben Sturmfels via

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h72agvee.fsf@sturm.com.au \
    --to=help-guix@gnu.org \
    --cc=ben@sturm.com.au \
    --cc=me@tobias.gr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).