This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: advise on future of glibc (mktime issue)
- From: Nix <nix at esperi dot org dot uk>
- To: Denis Vlasenko <vda at ilport dot com dot ua>
- Cc: "Jairo19 at interhosting dot us" <jairo19 at interhosting dot us>, Petter Reinholdtsen <pere at hungry dot com>, libc-alpha at sources dot redhat dot com
- Date: Wed, 08 Jun 2005 17:44:18 +0100
- Subject: Re: advise on future of glibc (mktime issue)
- References: <42A5B0C4.7010301@interhosting.us><42A5C27D.5080901@interhosting.us> <874qc94swj.fsf@amaterasu.srvr.nix><200506081709.24412.vda@ilport.com.ua>
On Wed, 8 Jun 2005, Denis Vlasenko said:
> On Wednesday 08 June 2005 03:02, Nix wrote:
>> Am I missing something? If not, I'll whip up a patch that does that
>> (against HEAD, as this is unlikely to be suitable for the stable branch:
>> I can roll one against 2.3.5 anyway, if Jairo wants).
>
> Maybe do not stat the file, but mmap it instead, and check for changes
> with memcmp()?
I think we should spot rm-and-replacement of /etc/localtime: wouldn't
that get broken? The last thing we want is for some processes to be
checking an unlinked file for changes... :/
--
`It's as bizarre an intrusion as, I don't know, the hobbits coming home
to find that the Shire has been taken over by gangsta rappers.'