From: Wido den Hollander <wido@42on.com>
To: Sage Weil <sage@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: disabling updatedb
Date: Tue, 18 Feb 2014 19:25:32 +0100 [thread overview]
Message-ID: <5303A59C.6030604@42on.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1402180845440.15052@cobra.newdream.net>
On 02/18/2014 05:47 PM, Sage Weil wrote:
> Dan at CERN noticed that his performance was tanking because updatedb was
> running against /var/lib/ceph. updatedb has a PRUNE line in
> /etc/updatedb.conf that we should presumably be adding ourselves to. One
> user pointed out a package that uses sed to rewrite this line in the init
> script on start.
>
> I have two questions:
>
> - is there no better way than sed to add ourselves to this list?
> - should we do it in the init script, or postinst, or both?
>
Well, I don't have a clue. postinst seems very dirty to me. It's a
bummer that updatedb doesn't support a .d directory for configuration.
> Presumably this is a problem others have solved with other packages.
>
> http://tracker.ceph.com/issues/7451
>
Not completely the same, but I filed something similar at Ubuntu
yesterday: https://bugs.launchpad.net/ubuntu/+source/mlocate/+bug/1281074
It's to prevent Ceph clients from indexing CephFS or Ceph Fuse.
Hopefully that makes it into 14.04.
> sage
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Wido den Hollander
42on B.V.
Phone: +31 (0)20 700 9902
Skype: contact42on
prev parent reply other threads:[~2014-02-18 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 16:47 disabling updatedb Sage Weil
2014-02-18 17:52 ` [Ceph-maintainers] " Gaudenz Steinlin
2014-02-18 18:20 ` Dan van der Ster
2014-02-18 22:07 ` bernhard glomm
2014-02-20 18:47 ` Sage Weil
2014-08-20 21:30 ` Dan Mick
2014-08-20 22:06 ` Sage Weil
2014-02-18 18:25 ` Wido den Hollander [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5303A59C.6030604@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.