Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-Id: <3.0.5.32.20020629183141.007fa560@mail.attbi.com> X-Sender: phumblet AT mail DOT attbi DOT com Date: Sat, 29 Jun 2002 18:31:41 -0400 To: cygwin-developers AT cygwin DOT com From: "Pierre A. Humblet" Subject: Re: Slowdown In-Reply-To: <20020629095714.D1247@cygbert.vinschen.de> References: <20020629031639 DOT GA14536 AT redhat DOT com> <3D1B4043 DOT EF2CA37A AT ieee DOT org> <3D1B4043 DOT EF2CA37A AT ieee DOT org> <3 DOT 0 DOT 5 DOT 32 DOT 20020627224059 DOT 0080d5b0 AT mail DOT attbi DOT com> <20020629031639 DOT GA14536 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 09:57 AM 6/29/2002 +0200, Corinna Vinschen wrote: >I think it's most sane to > >- Look for $HOME >- Try /etc/passwd >- Look for HOMEDRIVE/HOMEPATH >- Lookup on the server >- Give up, aka use HOME=/home/$username It's your baby, and you are a very good mother! What does linux do if you don't have HOME or home in /etc/passwd ? Seriously, the reason I wouldn't look up server on startup is to avoid what happened recently. Somebody was running happilly at the office but complained about slow start when running at home as a domain user detached from the network. I would still lookup the server after setuid (to set HOMEDRIVE/HOMEPATH), because the server must be available anyway to setuid to a domain user. Pierre