From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] Possible correction/clarification of FQA 8.4.7: secstore client
Date: Mon, 11 Mar 2024 15:00:54 +0100 (GMT+01:00) [thread overview]
Message-ID: <29f4f195-ed0c-42bf-98f1-a451499d05a9@sirjofri.de> (raw)
In-Reply-To: <922d324e-da66-4f34-b725-6cf863a4a68c@telia.com>
11.03.2024 14:43:48 orjan <oras9@telia.com>:
> After help from sirjofri on discourse and some man page reading I gradually started to understand the the error msg was correct. At this point the file doesn't exist.
>
> So my suggestion is to add:
>
> % touch factotum
>
> %auth/secsstore -p factotum
>
> before the line triggering the error msg.
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.
sirjofri
next prev parent reply other threads:[~2024-03-11 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 13:41 orjan
2024-03-11 14:00 ` sirjofri [this message]
2024-03-12 16:25 ` sl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29f4f195-ed0c-42bf-98f1-a451499d05a9@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).