From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 6F41926729 for ; Tue, 12 Mar 2024 17:29:09 +0100 (CET) Received: from gaff.inri.net ([168.235.71.243]) by 9front; Tue Mar 12 12:25:58 -0400 2024 Message-ID: Date: Tue, 12 Mar 2024 12:25:57 -0400 From: sl@stanleylieber.com To: 9front@9front.org In-Reply-To: <29f4f195-ed0c-42bf-98f1-a451499d05a9@sirjofri.de> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: extended rails cache SSL over JSON session scripting control Subject: Re: [9front] Possible correction/clarification of FQA 8.4.7: secstore client Reply-To: 9front@9front.org Precedence: bulk > I would vote for not changing the code example, but adding a clarifying comment: > > On the first run, auth/secstore -g factotum will result in an error because the file does not exist yet. This error can be ignored. this has been accomplished. sl