From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28606 invoked by alias); 3 Oct 2014 09:05:33 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 19206 Received: (qmail 29335 invoked from network); 3 Oct 2014 09:05:29 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_PASS autolearn=ham version=3.3.2 X-AuditID: cbfec7f4-b7f156d0000063c7-6f-542e66d5d800 Date: Fri, 03 Oct 2014 10:05:24 +0100 From: Peter Stephenson To: "Vadim A. Misbakh-Soloviov" , Zsh-Users List Subject: Re: freezing bug in 5.0.6? Message-id: <20141003100524.5725380b@pwslap01u.europe.root.pri> In-reply-to: <2866935.K4qTiKRXRF@note> References: <2866935.K4qTiKRXRF@note> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOLMWRmVeSWpSXmKPExsVy+t/xy7pX0/RCDGZ0KlpMfLyF2WLHyZWM Dkweu/7uYfJYdfADUwBTFJdNSmpOZllqkb5dAlfG7WNnWAr+slXMv7iGuYHxPGsXIyeHhICJ xOGGT8wQtpjEhXvr2boYuTiEBJYySpzb8YQRwulnkng1txesg0VAVeLJwVNgNpuAocTUTbMZ QWwRgRCJa62X2EBsYQFliTPd78FsXgF7ic5pLSwgNqeAmkTfklaweiGgObP3vQObwy+gL3H1 7ycmiCvsJWZeOcMI0Sso8WPyPbBeZgEtic3bmlghbHmJzWveMk9gFJiFpGwWkrJZSMoWMDKv YhRNLU0uKE5KzzXUK07MLS7NS9dLzs/dxAgJzC87GBcfszrEKMDBqMTD+/GGbogQa2JZcWXu IUYJDmYlEd7TcXohQrwpiZVVqUX58UWlOanFhxiZODilGhiVBc17uGbfqij87irz6tJc89tW hXWrvxZtaC1Y3L/rYbfS9m6nhxlx/3vE7tm9vMB7Z/uc7dNOOp/br/m8YeOZI2yrb3Q+PhR3 aPOECZc5RGfsO+zNvvLMroCF6/hbZ2RPCenivWG96MicbfezC09sPjTV+rXkwR2GF/79mnH0 jgXrHW2XEJ0foUosxRmJhlrMRcWJAEgUg84qAgAA On Fri, 03 Oct 2014 14:44:30 +0700 "Vadim A. Misbakh-Soloviov" wrote: > Hi there! > I'm using SHARE_HISTORY option. > > After recent upgrade to 5.0.6 (means, all was okay before it) few days ago, > I've got a strange bug: sometimes new sessions freezes on zsh start. There have beens some subsequent history locking fixes, in particular commit 4414e54ea7ffe50acca851c11c2ef49dc867c55d Author: Barton E. Schaefer Date: Sat Sep 6 22:10:30 2014 -0700 33116: followup to 32580 to prevent double-locking with shared or incremental history so this might be fixed. (Bart will comment later, he's eight hours behind but gets up and checks his mail much earlier than me.) It's probably worth asking whether you've got HISTFCNTLLOCK set, as the option that most obviously affects locking. It's fairly new and off by default. pws