Date: Fri, 31 Jan 2014 18:57:16 +0400 From: "Marat N.Afanasyev" <amarat@li.ru> To: John Baldwin <jhb@freebsd.org>, Yamagi Burmeister <lists@yamagi.org> Cc: stable@freebsd.org, yerenkow@gmail.com, freebsd-stable@freebsd.org Subject: Re: 10.0, csh history merge broken? Message-ID: <52EBB9CC.2080802@li.ru> In-Reply-To: <201401291214.56887.jhb@freebsd.org> References: <52E0E917.3060403@li.ru> <201401281147.15801.jhb@freebsd.org> <20140129090624.615af8881fe6df55c9663b5c@yamagi.org> <201401291214.56887.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
John Baldwin wrote:
> On Wednesday, January 29, 2014 3:06:24 am Yamagi Burmeister wrote:
>> 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.
>
> Bah, somehow I had thought I had seen the 'lock' keyword in tcsh on my
> HEAD box, but I don't see it there now.
>
So, can we hope to have these patches appear in HEAD and MFC to, at
least, -stable soon? ;)
--
SY, Marat
[-- Attachment #2 --]
0 *H
010 + 0 *H
i0-0m0
*H
010 UIL10U
StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0
130829080313Z
140829193716Z0O10U
IsC164JG3dq5RPEQ10Uamarat@li.ru10 *H
amarat@li.ru0"0
*H
0
OTOZo")
Oc3>_m.'buު-a>EF!tln>N6\j}KvIJuyck@I:{iͦ]/:[2'nϫ"k4*&P`R}&\00쇒3訵mj!!H9]IP/b2nka3ZrMrKw&҇7I6gZ5\Kʣ~߮fα 00 U0 0U0U%0++0U,Vay'S#0U#0Sr풜\|~5NԸQ0U0amarat@li.ru0LU C0?0;+70*0.+"http://www.startssl.com/policy.pdf0+00' StartCom Certification Authority0This certificate was issued according to the Class 1 Validation requirements of the StartCom CA policy, reliance only for the intended purpose in compliance of the relying party obligations.06U/0-0+)'%http://crl.startssl.com/crtu1-crl.crl0+009+0-http://ocsp.startssl.com/sub/class1/client/ca0B+06http://aia.startssl.com/certs/sub.class1.client.ca.crt0#U0http://www.startssl.com/0
*H
;QewY}qcC<LӐHX~4)b<%83]2>^Ѝq\)Dq?V^^;
4'|
m6ϒZDDaJ2 )h{b=i0^J;RPYlY?)Qt)a}^a, 7VZnu.YZ2)9>ye /qXO4Tw[8,Ԍz9^*:@_Ǡ,0{0400
*H
0}10 UIL10U
StartCom Ltd.1+0)U"Secure Digital Certificate Signing1)0'U StartCom Certification Authority0
071024210155Z
171024210155Z010 UIL10U
StartCom Ltd.1+0)U"Secure Digital Certificate Signing1806U/StartCom Class 1 Primary Intermediate Client CA0"0
*H
0
-).2AUGo#G
B|NDRpM-B=o-we5JQpa>O.#._<V
[~**pz~3WG .ᘟMlr[<Ce6fqO"uxfWN#uicgkv$Lb%y`_{`xK'GN 00U00U0USr풜\|~5NԸQ0U#0N@[i04hCA0f+Z0X0'+0http://ocsp.startssl.com/ca0-+0!http://www.startssl.com/sfsca.crt0[UT0R0'%#!http://www.startssl.com/sfsca.crl0'%#!http://crl.startssl.com/sfsca.crl0U y0w0u+70f0.+"http://www.startssl.com/policy.pdf04+(http://www.startssl.com/intermediate.pdf0
*H
}x,\c^#wMq}>UK/^yX֏y frMIŲB61ymQҨݬZ0&