Date: Wed, 29 Jan 2014 09:06:24 +0100 From: Yamagi Burmeister <lists@yamagi.org> To: jhb@freebsd.org Cc: stable@freebsd.org, yerenkow@gmail.com, freebsd-stable@freebsd.org, amarat@li.ru Subject: Re: 10.0, csh history merge broken? Message-ID: <20140129090624.615af8881fe6df55c9663b5c@yamagi.org> In-Reply-To: <201401281147.15801.jhb@freebsd.org> References: <52E0E917.3060403@li.ru> <20140126215845.3b62debf03dade433622e9ba@yamagi.org> <CAPJF9wka3oaneuJ1Xq6fquQaK68SgS%2BkpvB62KLbs89dFWQ62w@mail.gmail.com> <201401281147.15801.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 Jan 2014 11:47:15 -0500 John Baldwin <jhb@freebsd.org> wrote: > On Monday, January 27, 2014 3:55:53 am Alexander Yerenkow wrote: > > >Maybe it would be a good idea to cherry pick those two revisions and > > >merge then into FreeBSD, until a new tcsh version is released. > > > > I think this is must, since currently any regular shutdown can break login > > ability (if server is high loaded + history file is broken and big enough). > > I have now locked history file with chflags until fix will come. > > These changes are already present in HEAD (FreeBSD 11) and will probably > be merged by the next 10 release. Really? As far as I can see the last commit to head/contrib/tcsh was the update to 6.18.01 one 22/02/2012 by mp@. While 6.18.01 featured a new, much faster history merge logic which minimized the race window, the root cause wasn't solve. Only the two upstream commits (from 08/12/2013 and 11/12/2013) linked above brought real locking to the merge process, serializing it between several tcsh instances. -- Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140129090624.615af8881fe6df55c9663b5c>