From: Thomas Schweikle <tschweikle@bfs.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Cygwin starts take long since march. Three minutes to prompt.
Date: Mon, 3 Apr 2023 16:10:05 +0000 [thread overview]
Message-ID: <0c114a30-b97d-6175-8bae-eb3767d129a1@bfs.de> (raw)
In-Reply-To: <b6c0b4e6-17be-2759-83bc-89aac4f4fcab@Shaw.ca>
[-- Attachment #1.1.1: Type: text/plain, Size: 4025 bytes --]
Am Mo., 03.Apr..2023 um 17:48:03 schrieb Brian Inglis via Cygwin:
> On 2023-04-03 08:59, Thomas Schweikle via Cygwin wrote:
>> Am Mo., 03.Apr..2023 um 16:47:42 schrieb Eliot Moss:
>>> On 4/3/2023 10:38 AM, Thomas Schweikle via Cygwin wrote:
>>>> Cygwin shell takes about three minutes until the prompt is shown.
>>>> Any idea how to find out the cause?
>
>>> I think the most common thing in the past had to do with
>>> probing remote mounts. You could try pruning paths and
>>> see what happens, or adjusting mount parameters.
>
>> Mounts are:
>> $ cat /proc/mounts
>> C:/cygwin/bin /usr/bin ntfs binary,auto 1 1
>> C:/cygwin/lib /usr/lib ntfs binary,auto 1 1
>> C:/cygwin / ntfs binary,auto 1 1
>> C: /cygdrive/c ntfs binary,posix=0,user,noumount,auto 1 1
>> G: /cygdrive/g netapp binary,posix=0,user,noumount,auto 1 1
>> L: /cygdrive/l netapp binary,posix=0,user,noumount,auto 1 1
>> M: /cygdrive/m netapp binary,posix=0,user,noumount,auto 1 1
>> O: /cygdrive/o netapp binary,posix=0,user,noumount,auto 1 1
>> P: /cygdrive/p netapp binary,posix=0,user,noumount,auto 1 1
>> T: /cygdrive/t netapp binary,posix=0,user,noumount,auto 1 1
>> V: /cygdrive/v netapp binary,posix=0,user,noumount,auto 1 1
>> W: /cygdrive/w netapp binary,posix=0,user,noumount,auto 1 1
>> X: /cygdrive/x netapp binary,posix=0,user,noumount,auto 1 1
>> Y: /cygdrive/y netapp binary,posix=0,user,noumount,auto 1 1
>> Z: /cygdrive/z netapp binary,posix=0,user,noumount,auto 1 1
>
>> I've read somewhere noacl should be given for these mounts. Could not
>> find it, even with a fresh installed cygwin on a fresh windows.
>
>> Trying to reset acls to defaults for "C:\cygwin" gives lots of "access
>> denied" errors, even if running as "Administrator" from an elevated
>> shell. Tried both "cmd.exe" and "powershell.exe". Both did not allow
>> to change acls.
>
>> Seems as if "C:\cygwin" has lost ownership an some acls. Any idea to
>> get them back in place for the whole tree?
>
> Should not need anything special:
>
> $ ls -dl / && getfacl / && icacls `cygpath -m /` # sanitized:
> drwxr-xr-x 1 $USER None 0 Mar 16 18:57 /
>
> # file: /
> # owner: $USER
> # group: None
> user::rwx
> group::r-x
> other::r-x
> default:user::rwx
> default:group::r-x
> default:other::r-x
>
> C:/.../cygwin64 $HOSTNAME/$USER:(F)
> $HOSTNAME/None:(RX)
> Everyone:(RX)
> CREATOR OWNER:(OI)(CI)(IO)(F)
> CREATOR GROUP:(OI)(CI)(IO)(RX)
> Everyone:(OI)(CI)(IO)(RX)
>
> Successfully processed 1 files; Failed processing 0 files
$ ls -dl / && getfacl / && icacls `cygpath -m /`
drwxr-xr-x 1 SYSTEM SYSTEM 0 Mar 23 13:44 /
# file: /
# owner: SYSTEM
# group: SYSTEM
user::rwx
group::r-x
other::r-x
default:user::rwx
default:group::r-x
default:other::r-x
C:/cygwin NT-AUTORITÄT\SYSTEM:(F)
NT-AUTORITÄT\SYSTEM:(RX)
Jeder:(RX)
ERSTELLER-BESITZER:(OI)(CI)(IO)(F)
ERSTELLERGRUPPE:(OI)(CI)(IO)(RX)
Jeder:(OI)(CI)(IO)(RX)
1 Dateien erfolgreich verarbeitet, bei 0 Dateien ist ein
Verarbeitungsfehler aufgetreten.
Is this ok? Not missing "Administrator"?
> Those kinds of delays are often AD lookup for domain users and groups:
> see /etc/nsswitch.conf for settings, and consider running cygserver at
> system or Cygwin startup to preload and cache the info.
$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# This file is read once by the first process in a
# Cygwin process tree.
# To pick up changes, restart all Cygwin processes.
# For a description see https://cygwin.com/cygwin-ug-
# net/ntsec.html#ntsec-mapping-nsswitch
#
# Defaults:
# passwd: files db
# group: files db
# db_enum: cache builtin
# db_home: /home/%U
# db_shell: /bin/bash
# db_gecos: <empty>
It is at defaults.
--
Thomas
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2521 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 321 bytes --]
next prev parent reply other threads:[~2023-04-03 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 14:38 Thomas Schweikle
2023-04-03 14:47 ` Eliot Moss
2023-04-03 14:59 ` Thomas Schweikle
2023-04-03 15:48 ` Brian Inglis
2023-04-03 16:10 ` Thomas Schweikle [this message]
2023-04-03 18:34 ` 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=0c114a30-b97d-6175-8bae-eb3767d129a1@bfs.de \
--to=tschweikle@bfs.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).