From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: zp_man-db-update-index.dash creates C:\cygwin64\%SystemDrive%
Date: Wed, 24 Nov 2021 11:30:50 -0700 [thread overview]
Message-ID: <421ff14f-5a3a-fd0c-0e27-0d82cb4ffe9d@SystematicSw.ab.ca> (raw)
In-Reply-To: <8735nla01p.fsf@Rainer.invalid>
On 2021-11-24 11:19, Achim Gratz wrote:
> Leonid Vladimirovič Mironov via Cygwin writes:
>> Recently when cygwin setup runs windows 10 started creating
>> "C:\cygwin64\%SystemDrive%\ProgramData\Microsoft\Windows\Caches"
>> folder - exactly like that, with %SystemDrive% not expanded,
>> containing the following files
> […]
>> Turned out that the culprit is the
>> /etc/postinstall/zp_man-db-update-index.dash script which runs at the
>> end of every setup session, although I couldn't figure why: it just
>> runs mandb with some fancy redirection and nothing untoward happens
>> when it is run manually and with admin privileges, but the folder in
>> question was never created until I ran mandb to create man index which
>> for some reason was not created automatically during installation, and
>> when /var/cache/man/index.db is removed which effectively disables
>> this script this folder is not created. I am baffled.
>
> Me too. Apparently this is some bug deep in the bowels of Windows that
> triggers when neither SystemDrive nor ProgramData are defined in the
> environment and a new console session gets created. It seems I can work
> around getting the extra directories created by defining SystemDrive in
> a certain nonsensical way, but it really is an ugly hack; I'll have to
> see if there's a better fix.
Problem mentioned by me some time ago, may be related to this, from
undocumented mandb handling of Windows localization catalog folders:
https://cygwin.com/pipermail/cygwin/2018-January/235776.html
which may include moving "stray cats" (also undocumented) to / [Cygwin]
root so they get noticed and handled?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2021-11-24 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 9:06 Миронов Леонид Владимирович
2021-11-24 17:31 ` Brian Inglis
2021-11-24 18:23 ` Achim Gratz
2021-11-24 18:34 ` Brian Inglis
2021-11-24 19:54 ` Achim Gratz
2021-11-25 7:59 ` Brian Inglis
2021-11-25 18:51 ` Achim Gratz
2021-11-28 23:17 ` Brian Inglis
2021-11-29 9:52 ` ASSI
2021-11-24 18:19 ` Achim Gratz
2021-11-24 18:30 ` Brian Inglis [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=421ff14f-5a3a-fd0c-0e27-0d82cb4ffe9d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).