From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: man-db-2.10.0-1
Date: Tue, 08 Feb 2022 21:00:30 +0100 [thread overview]
Message-ID: <87v8xp9li9.fsf@Rainer.invalid> (raw)
In-Reply-To: <87zgn19okn.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 08 Feb 2022 19:54:16 +0100")
Achim Gratz writes:
> Well, that file it tries to create is a temporary file (the filename is
> the PID of the process creating it), so if that same process can create
> directories and files, but then fails to create abother file, something
> else must be interfering with it.
The particular error message would appear if the file operation
encountered an error other than EACCESS, EROFS, EAGAIN or EWOULDBLOCK.
If you strace mandb you might be able to see what that error actually is
(or it might simply work).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
prev parent reply other threads:[~2022-02-08 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 20:45 Achim Gratz
2022-02-07 18:58 ` Andrey Repin
2022-02-07 20:35 ` Achim Gratz
2022-02-07 20:53 ` Achim Gratz
2022-02-08 10:18 ` Andrey Repin
2022-02-08 18:54 ` Achim Gratz
2022-02-08 20:00 ` Achim Gratz [this message]
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=87v8xp9li9.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).