From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.2 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id AF66D20248 for ; Fri, 15 Mar 2019 13:13:08 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:from:to:cc:date:in-reply-to :references:content-type:mime-version:content-transfer-encoding :subject; q=dns; s=default; b=LzXj4c+LS3D7H7049mNz0cZwrliQcEa+YZ cqA9SxPqpZzIVMKAZu9tvwW7R113Ee7k5+jbxNAtIniTC79BlGuyD46G7nesKaIm 7L0uFZZlpO9vkUoF26Gvz+5XYXfyiOKoJfAC3faxsrLcCG4AGbnuVXSgkzb760Qm AytZsOhe4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:from:to:cc:date:in-reply-to :references:content-type:mime-version:content-transfer-encoding :subject; s=default; bh=VsFdcO5KQuRuFfD4/gbeslC8FTM=; b=QYq+5tPv WBWOnkLrF+x8ILd45hGF6kIsj+7RsgAIOxhsDEW1kyFDe2Ayg8aqtUQNrqa8p0JV 8jGIoZqKEBAFhK4tPqqgeyy3fR8nT4EsD+MXDm9L1Npm5R2rdUcAo3FJINwObH+f B0oTuzN3gsSl0VrpWJSnbPGb+sOjO+sD/60= Received: (qmail 63830 invoked by alias); 15 Mar 2019 13:13:06 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 63819 invoked by uid 89); 15 Mar 2019 13:13:05 -0000 Authentication-Results: sourceware.org; auth=none X-HELO: ou.quest-ce.net Message-ID: <683f2a6c6a5cb4543545ff1253fa67ceee1deec7.camel@opteya.com> From: Yann Droneaud To: Florian Weimer , Paul Eggert Cc: libc-alpha@sourceware.org Date: Fri, 15 Mar 2019 14:12:56 +0100 In-Reply-To: <877ed1uwal.fsf@oldenburg2.str.redhat.com> References: <20190211163728.31655-1-eggert@cs.ucla.edu> <87h8d1e8tk.fsf@oldenburg2.str.redhat.com> <9f3882f6-e056-95d1-4506-58fd87cbf6c2@cs.ucla.edu> <87d0muesi3.fsf@oldenburg2.str.redhat.com> <4d46da6e-6901-f736-f573-3dfbef27a3df@cs.ucla.edu> <87d0mt5yxa.fsf@oldenburg2.str.redhat.com> <877ed1uwal.fsf@oldenburg2.str.redhat.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.31.91 (3.31.91-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 2a01:e35:2e9f:6cb0:857c:11e6:3194:d53d X-SA-Exim-Mail-From: ydroneaud@opteya.com Subject: Re: [PATCH] Fix multiple minor tzset glitches [BZ #24004] X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on ou.quest-ce.net) Hi, Le jeudi 14 mars 2019 à 19:48 +0100, Florian Weimer a écrit : > * Paul Eggert: > > 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? :-) > > With the mapped file, there is no file polling as such, just a few > memory loads. The cost is that the system administrator needs to run a > command after updating any of the covered configuration files, which is > why this has to be optional (and opt-in per configuration file). There > probably aren't that many configuration files where this is needed. > I think there's a caveat with memory mapped file: if a new version of the configuration file is created and renamed to the configuration location, replacing the previous one, applications won't notice the update, as the memory mapping will still reference the previous file. Regards. -- Yann Droneaud OPTEYA