From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Problems installing man-db
Date: Fri, 20 Jun 2014 04:38:00 -0000 [thread overview]
Message-ID: <87oaxoureg.fsf@Rainer.invalid> (raw)
In-Reply-To: <53A37DEE.8050103@breisch.org> (Chris J. Breisch's message of "Thu, 19 Jun 2014 20:18:54 -0400")
Chris J. Breisch writes:
> Achim Gratz wrote:
>> Crashed the same way as the postinstall script. However, "mandb -dc" ran
>> through and the postinstall script now finishes.
>>
> Odd. Ok, I'll do some digging into this and see what I can find. I can
> change the postinstall script to do a "mandb -dc" for now, I
> guess. The "-d" output goes to stderr, I see.
Based on the characteristics of the crash I'd say that there is a race
somewhere and the debug output serializes things enough for this not to
become a problem. It didn't even appreciably slow down the creation of
the database from what I could tell. NB: I was testing on a quad-core
w/ SSD, but the mandatory virus scanner inserts itself on each file
operation of course.
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
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-06-20 4:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 23:32 Angelo Graziosi
2014-06-19 0:14 ` Chris J. Breisch
2014-06-19 16:35 ` Achim Gratz
2014-06-19 16:57 ` Achim Gratz
2014-06-20 0:19 ` Chris J. Breisch
2014-06-20 4:38 ` Achim Gratz [this message]
2014-06-19 12:45 Angelo Graziosi
2014-06-19 13:21 ` Shaddy Baddah
2014-06-19 15:39 ` Chris J. Breisch
2014-06-19 14:42 Angelo Graziosi
2014-06-19 19:58 Angelo Graziosi
2014-06-20 0:19 ` Chris J. Breisch
2014-06-23 22:55 ` Jon Bailey
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=87oaxoureg.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).