public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: zp_man-db-update-index.dash creates C:\cygwin64\%SystemDrive%
Date: Mon, 29 Nov 2021 10:52:48 +0100	[thread overview]
Message-ID: <87fsrfqoen.fsf@Otto.invalid> (raw)
In-Reply-To: <565ef64a-b9ed-eca5-b473-cfe2a761559b@SystematicSw.ab.ca> (Brian Inglis's message of "Sun, 28 Nov 2021 16:17:40 -0700")

Brian Inglis writes:
> I'll create a new 0p_man-db-patch.dash script to add -d after mandb
> postinstall to produce diagnostic output, and get back.

Just add that flag to the already provided postinstall script.

> I previously had a patch script to add around mandb in postinstall:
>
> 	/usr/bin/nohup ... /usr/bin/mandb ... &

That doesn't work when run from setup.  The process will abort when
setup exits.

> which did not create any artifacts I believe but can not be sure of
> timing, and that could be an option for your script instead of
> cygstart?

I'm not sure why you're harping on cygstart, but if you want to avoid it
just install the package that makes the mandb update synchronous.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  reply	other threads:[~2021-11-29  9:52 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 [this message]
2021-11-24 18:19 ` Achim Gratz
2021-11-24 18:30   ` Brian Inglis

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=87fsrfqoen.fsf@Otto.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).