unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Fix multiple minor tzset glitches [BZ #24004]
Date: Thu, 14 Mar 2019 09:47:30 -0700	[thread overview]
Message-ID: <b0b2acf2-217e-5d27-8dad-094bae44abed@cs.ucla.edu> (raw)
In-Reply-To: <87d0mt5yxa.fsf@oldenburg2.str.redhat.com>

On 3/14/19 7:10 AM, Florian Weimer wrote:
> * Paul Eggert:
>
>> Yes, and it would be good to add a way to control polling of /etc files,
>> and whatever method is used to control polling of /etc/nsswitch.conf
>> etc. could also be used to control polling of /etc/localtime.
> I think this should be a configuration file.  We can use a shared
> mapping (or use /etc/ld.so.cache) to make up-to-date checks really,
> really cheap.  But I think we should apply this mechanism only to files
> where the system administrator has enabled this feature.

Will the configuration file will have also an entry to control whether
the configuration file itself is polled? :-)

Come to think of it, this has the same feel as the other tunables, so
perhaps it'd be better to add it to the tunables feature. Something like
this:

export GLIBC_TUNABLES='glibc.etcpoll.nsswitch=1'

in order to enable polling of /etc/nsswitch.conf.


  reply	other threads:[~2019-03-14 16:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 16:37 [PATCH] Fix multiple minor tzset glitches [BZ #24004] Paul Eggert
2019-02-18  9:37 ` Florian Weimer
2019-02-20 19:29   ` Paul Eggert
2019-03-13 14:52     ` Florian Weimer
2019-03-13 17:02       ` Paul Eggert
2019-03-14 14:10         ` Florian Weimer
2019-03-14 16:47           ` Paul Eggert [this message]
2019-03-14 18:24             ` Adhemerval Zanella
2019-03-14 18:48             ` Florian Weimer
2019-03-15 13:12               ` Yann Droneaud
2019-03-15 15:05                 ` Florian Weimer
2019-03-15 16:01                   ` Yann Droneaud
2019-04-10 11:57     ` Florian Weimer
2019-04-10 13:18       ` Carlos O'Donell
2019-04-11 17:51         ` Paul Eggert
2019-04-12 17:07           ` Carlos O'Donell
2019-04-12 18:41             ` Paul Eggert
2019-04-12 18:57               ` Carlos O'Donell
2019-04-12 19:26                 ` Florian Weimer

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://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=b0b2acf2-217e-5d27-8dad-094bae44abed@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    /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).