From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31715 invoked from network); 2 Oct 2021 23:20:54 -0000 Received: from zero.zsh.org (2a02:898:31:0:48:4558:7a:7368) by inbox.vuxu.org with ESMTPUTF8; 2 Oct 2021 23:20:54 -0000 ARC-Seal: i=1; cv=none; a=rsa-sha256; d=zsh.org; s=rsa-20210803; t=1633216854; b=HC+l0QiiFQPEAZ27O5MJO3UggcYnmNXcPU+y4ZAdFtG7HWuy/t7sB3JHbdVUXfEAT65/1c72BO RcLXUSxYI/EjSuameCOySZOz9/k5mheTIpze9+WSy3oZ+mzAm2t7e4nmN0F6f+zuUovPrj27Yr WxzrkGUrDo5/phoVHgXBlVi8ClvJCryX4fVYtGZ+cfkqTnayY0JXUDEMDFABoTY5/oGGUEw75Q PzjJ/F8E5BXJa6/Ly05yKQyBKVX6dG622bUhHdWCTtxqLZdt5GwcGZWc0KfQi0CdAChrZe22+8 X1yIDmY+dxltjE6mlIJmbA4xP9SlsrZ0RkSHIhABRBrPnw==; ARC-Authentication-Results: i=1; zsh.org; iprev=pass (mail-il1-f172.google.com) smtp.remote-ip=209.85.166.172; dkim=pass header.d=gmail.com header.s=20210112 header.a=rsa-sha256; dmarc=pass header.from=gmail.com; arc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed; d=zsh.org; s=rsa-20210803; t=1633216854; bh=hZba7/caAU42O4aDQatZ+3d82KZ1E64zsE4RKA12fqs=; h=List-Archive:List-Owner:List-Post:List-Unsubscribe:List-Subscribe:List-Help: List-Id:Sender:Content-Type:Cc:To:Subject:Message-ID:Date:From:In-Reply-To: References:MIME-Version:DKIM-Signature:DKIM-Signature; b=pNZ6gmfV7bfvwC8eCdPDMIopBs/4gExhY2A0D1vfr4YqHygYe2HDzI297HJI7Trs+UT9D5QWgP oy+wfhiAv2PjCQoT4R/iM5lUk21r25HC9MSQpMP/jUKto5h2JVEgzYa6zRKJCys4C1650APeur +5kehVxuZzPj8lWX14z31QqPyjr1PhRvUtqfG881JmM9vWejqsQ0BQwznDwBzSPRMXLOYEWOB/ vC5GSTfxz2E/gk8kLy5qtMUKCn3VjXobG1ck7bAUEIUADWAwVN9HkVCEr4/lnAFU3Fyj1amk+p 5xLaoWkcb6eEQUZitMkZHSPyy7i1QPv8u9swzmz2cK3oOg==; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=zsh.org; s=rsa-20210803; h=List-Archive:List-Owner:List-Post:List-Unsubscribe: List-Subscribe:List-Help:List-Id:Sender:Content-Type:Cc:To:Subject:Message-ID :Date:From:In-Reply-To:References:MIME-Version:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID; bh=PSVTcF9ICQCKAhvwKeYl/ZzgEatVQn7T8iX0BmJngRM=; b=ppUGppWIa10aI9D0UC4GpKyBDR +WbggU3diKakeyDFyabuafKxi+ooWzLvJSTDBJAi7oBfxfYB39MfUX6Jeg7YObjN2doNrt3aATRyi J1Ev3HzX4zZ/seIFlR9YQvC8Ek4Xa9jjvqcVGrMTw5of249vVlX0AaTDjOU/93CtSYaT5VMMU/g8k NW1zxaZkShr3hMFtICjuuY+MCqawq/9BXnRMwnUsfY3KLIgwz5GAxt7g0EkLZcUMvQHMMlU7mcRUA NU/CURoAmpi3/MKghMejadCa9P5InV417CnILR3R4TLP5FeBTYkQFRD32Gu0Kw58mwqIUjcmWxdMb 4Oj7l/7A==; Received: from authenticated user by zero.zsh.org with local id 1mWoJK-000NbY-3G; Sat, 02 Oct 2021 23:20:54 +0000 Authentication-Results: zsh.org; iprev=pass (mail-il1-f172.google.com) smtp.remote-ip=209.85.166.172; dkim=pass header.d=gmail.com header.s=20210112 header.a=rsa-sha256; dmarc=pass header.from=gmail.com; arc=none Received: from mail-il1-f172.google.com ([209.85.166.172]:38792) by zero.zsh.org with esmtps (TLS1.3:TLS_AES_128_GCM_SHA256:128) id 1mWoIV-000MtJ-ST; Sat, 02 Oct 2021 23:20:04 +0000 Received: by mail-il1-f172.google.com with SMTP id r9so14427652ile.5 for ; Sat, 02 Oct 2021 16:20:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PSVTcF9ICQCKAhvwKeYl/ZzgEatVQn7T8iX0BmJngRM=; b=AuA0jDDR8xLDkG/mbz5svXOIbqZ86UAo9Nk9SIZWgdb4kRxecr8xpUAPD+bPtCrp/I WwZaOXt2y1guuE+5ITDZ+1xxy2FGh3Sl+zzHboIfuAvJ/VTr36hDI+N2SaHU3g6Mh2Re UELEnSMuLwLqI2Pe4FpMP622ChJKOWjdP5tcsZI1X6AjqT75wcAU3BL62wCnSErosV1I kOEehkqkiVSQj7zIlxMf/XO5ZNCyKz+j1H8KNjwqv3C1WRodtu/aGkLWpOAvFJ0IwHlx 5NOy19jFR8XTnHFDmxwX576/VGhenWfF6t/jIdFxvzj3OPPCPG7nowjkj67XeqHPsvru te1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PSVTcF9ICQCKAhvwKeYl/ZzgEatVQn7T8iX0BmJngRM=; b=Q+vn+dv9IBzCxuFn+djOBfaKyzRORPtEukDLsiSkq4e5y0h6/jSHkyt5lsU9KDW0qn 1ZyZy/AJa1e16qNtSnndeU3Cf3IXHc2mFq0vvdV6SMbLNOBu2J8R3z0z+AiZTFNBbbo8 XUlPnSuU9e81Y+uV3Y4kotO6kbUui4Jp6CEZZPNGyHR+B9PpFECH7yYbXtIGMRPOItPK xTLgYef8VEUyiFO9FqBWsSAFlUZ0tBBDQ8GP8biNwBfgFjVyhxz5nelebnqP266J+uKD UrJJeSBaY8TP0S5t9be23dX4YCJct2OA9ZPW/cCYMa9mELedAz6x+nEOIKbDLGLzVCDv a8nQ== X-Gm-Message-State: AOAM531hKR0egqAVfAEhSx7TC/xbMMWDI5H66qHHfL9mqSGOq7vvcNqy uryxVKc4H4hLJztFToc7t5hxiBJure7pgreSDPA= X-Google-Smtp-Source: ABdhPJwy4aH4mg9tSS4fso53gwli3h4jX/a3NghuXuR3aSKPKqfo2SrHmmwifN2uZd7WmW1o/Kka4dR9EoZx6i7gzrY= X-Received: by 2002:a05:6e02:1bad:: with SMTP id n13mr4001367ili.142.1633216802450; Sat, 02 Oct 2021 16:20:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Pier Paolo Grassi Date: Sun, 3 Oct 2021 01:19:51 +0200 Message-ID: Subject: Re: shared history file To: Bart Schaefer Cc: Zsh-Users List Content-Type: multipart/alternative; boundary="00000000000059f0a705cd66ebc4" X-Seq: 27218 Archived-At: X-Loop: zsh-users@zsh.org Errors-To: zsh-users-owner@zsh.org Precedence: list Precedence: bulk Sender: zsh-users-request@zsh.org X-no-archive: yes List-Id: List-Help: List-Subscribe: List-Unsubscribe: List-Post: List-Owner: List-Archive: --00000000000059f0a705cd66ebc4 Content-Type: text/plain; charset="UTF-8" thanks, I was hoping for a different answer but it is what it is Il giorno dom 3 ott 2021 alle 01:12 Bart Schaefer ha scritto: > On Sat, Oct 2, 2021 at 10:53 AM Pier Paolo Grassi > wrote: > > is it possibile in zsh to disable locking the history file during write > operations? I am the only one writing to those files so I shouldn't risk a > concurrent operation. > > The lock mechanism is not to protect against multiple users writing > those files, it's to protect against multiple zsh processes writing to > the files. E.g. if you have more than one window open on the same > "project", both zsh might attempt to write the file, even though you > are "the only one" who needs to write. > > The problem here seems to be that your host system has symbolic links, > so zsh is compiled to use that locking mechanism, but the remote > server doesn't support creating one. > > Your best bet is to store the project history in a directory where a > symbolic link can be created, instead of storing it inside the > remote-mounted directory. > > The ~/.zlogin file is sourced before, and the ~/.zlogout file after, > reading/saving history respectively, so if you need to copy the file > contents from/to the remote directory to/from the file used by the > current shell, you can do so there ... or in whatever other functions > etc. you are using to keep track of which project you're in. > -- Pier Paolo Grassi --00000000000059f0a705cd66ebc4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
thanks, I was hoping for a different answer but it is wha= t it is

Il giorno dom 3 ott 2021 alle 01:12 Bart Schaefer <schaefer@brasslantern.com> ha = scritto:
On Sat, Oct 2, 2021 at 10:53 AM Pier Pao= lo Grassi <pie= rpaolog@gmail.com> wrote:
> is it possibile in zsh to disable locking the history file during writ= e operations? I am the only one writing to those files so I shouldn't r= isk a concurrent operation.

The lock mechanism is not to protect against multiple users writing
those files, it's to protect against multiple zsh processes writing to<= br> the files.=C2=A0 E.g. if you have more than one window open on the same
"project", both zsh might attempt to write the file, even though = you
are "the only one" who needs to write.

The problem here seems to be that your host system has symbolic links,
so zsh is compiled to use that locking mechanism, but the remote
server doesn't support creating one.

Your best bet is to store the project history in a directory where a
symbolic link can be created, instead of storing it inside the
remote-mounted directory.

The ~/.zlogin file is sourced before, and the ~/.zlogout file after,
reading/saving history respectively, so if you need to copy the file
contents from/to the remote directory to/from the file used by the
current shell, you can do so there ... or in whatever other functions
etc. you are using to keep track of which project you're in.
--
Pier Paolo Grassi
--00000000000059f0a705cd66ebc4--