From: Maayan Apelboim <Maayan.Apelboim@clarizen.com>
To: "Brian.Inglis@SystematicSw.ab.ca"
<Brian.Inglis@SystematicSw.ab.ca>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: getent doesn't work properly
Date: Wed, 13 Nov 2019 15:18:00 -0000 [thread overview]
Message-ID: <AM4PR07MB34730BB3D998CF6B47BA84D495760@AM4PR07MB3473.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <9ac40199-8d4a-206d-4081-a6057e357405@SystematicSw.ab.ca>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1435 bytes --]
Hi,
Well it might help, but since I don't have this installed in any other envs and everything is working fine I prefer to try as a last resort.
If I won't be able to find the root cause I'll try this as well.
Thanks!
>> Why do I need cygserver?
> You don't exactly NEED cygserver. But if you have 1. Domain (or even
> multi-domain) environment.
> 2. and/or remote/slow/flaky connection to the domain server.
> cygserver may provide a smoother experience as it caches some
> information related to names resolution.
Running cygserver will also cache info and speed up processing if you run many:
- service daemons under Cygwin, especially cron jobs or ssh sessions
- concurrent processes, especially deeply nested, forked, or background
(some cron jobs background subprocesses *heavily* to reduce run time)
- XSI IPC message queues
- semaphores
- shared memory segments
otherwise that has to be managed by either the process itself or the root parent process, possibly in parallel threads.
--
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.
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒ÷\a&ö&ÆV×2æFÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöf\x17\x12ðФFö7VÖVçF\x17Föã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöFö72æFÖÀÐ¥Vç7V'67&&R\x06æfó¢\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöÖÂò7Vç7V'67&&R×6×\x06ÆPÐ Ð
next prev parent reply other threads:[~2019-11-13 12:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:02 Maayan Apelboim
2019-10-17 12:23 ` Jose Isaias Cabrera
2019-10-17 13:02 ` Maayan Apelboim
2019-10-17 16:55 ` Jose Isaias Cabrera
2019-10-18 12:44 ` Brian Inglis
2019-10-18 10:52 ` Corinna Vinschen
2019-10-23 11:17 ` Maayan Apelboim
2019-10-23 11:42 ` Corinna Vinschen
2019-10-23 13:28 ` Brian Inglis
2019-10-23 13:33 ` Maayan Apelboim
2019-10-24 14:06 ` Corinna Vinschen
2019-10-28 8:56 ` Maayan Apelboim
2019-11-13 12:04 ` Maayan Apelboim
2019-11-13 12:08 ` Maayan Apelboim
2019-10-18 11:05 ` Andrey Repin
2019-10-22 8:22 ` Maayan Apelboim
2019-10-28 17:35 ` Andrey Repin
2019-10-29 0:03 ` Brian Inglis
2019-11-13 15:18 ` Maayan Apelboim [this message]
2019-11-25 13:29 ` Maayan Apelboim
2019-11-25 15:24 ` Maayan Apelboim
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=AM4PR07MB34730BB3D998CF6B47BA84D495760@AM4PR07MB3473.eurprd07.prod.outlook.com \
--to=maayan.apelboim@clarizen.com \
--cc=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).