X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=nDlKll9WL1zozfPE
	q0SEwIJWCDIlxe67J5RogtyuHSIFF/pcb+J9W3CKlEdrA1I2U5QqarSI8/JD0395
	5AR39+aymQpL/dzS+QHbeNhI1lfaKRLBkcCIlvDMdY8jdEStRBXhxkY8Whs1+pX5
	u6i1+4lbwzVw5RS7fqkySpPXG+0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=3gU/wKq6MemgCJx8neV82F
	K2YVk=; b=QkrJcDxvfWn+Yy6Q1Qqevq4rd8z/DfPzQFwV52Tn60zJT3ZWhdPrOV
	bd/hC6r4nlW49NiqtY3tRRLOu1kt3H67lOieeyjPf0tMaE5cfv9Jg1vjeCytiTJ0
	T2RbEUFOcUhERMnIMv38HFvar3ziywnyno5bST4TYmOhx0pjjF32A=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_BODY_URIBL_PCCC,KAM_FROM_URIBL_PCCC,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtp.ht-systems.ru
Date: Fri, 5 Dec 2014 23:11:47 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1423715977.20141205231147@yandex.ru>
To: Corinna Vinschen <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Re: Cygwin AD integration home/shell changes
In-Reply-To: <20141205101302.GI3810@calimero.vinschen.de>
References: <0B8D23F7-0258-472D-BF38-860402FD3CDC@etr-usa.com>   <20141111101821.GO2782@calimero.vinschen.de>  <loom.20141111T112847-576@post.gmane.org>  <20141111111437.GB28012@calimero.vinschen.de>  <20141126205658.GA9157@calimero.vinschen.de>  <946685207.20141203102637@yandex.ru>  <20141203091608.GA26844@calimero.vinschen.de>  <118770258.20141203164448@yandex.ru>  <20141204094054.GC3810@calimero.vinschen.de>  <1682125876.20141205080743@yandex.ru>  <20141205101302.GI3810@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Corinna Vinschen!

>> >> >> > Here's what you get:
>> >> >> 
>> >> >> I finally realized, what was tingling me all this time.
>> >> >> The implicit fallback mechanics. I'd rather want to have explicit declaration
>> >> >> and a failure message in case something isn't right. Much easier to fix system
>> >> >> issues, when the system tell you about them.
>> >> 
>> >> > The fallback mechanism is pretty much required to have a sane default
>> >> > which works for home users without having to change nsswitch.conf at
>> >> > all.  Also, not everybody will want error messages rather than some sane
>> >> > fallback (for any given value of "sane"), while if you don't want a sane
>> >> > fallback, you can easily create an unsane fallback to help you maintain
>> >> > your solution, e.g.
>> >> 
>> >> >   db_home: cygwin /invalid/read-only-path
>> >> 
>> >> Why not set defaults (in case of db_home) to
>> >> 
>> >> db_home: cygwin desc /home/%U
>> >> 
>> >> and remove fallback?
>> >> It just not seems right - creating workarounds to implement straight behavior.
>> 
>> > It's not a workaround from my POV to provide a fallback.  Creating a
>> > workable passwd entry is important.  If I implement it as you suggest
>> > above, I would still provide the typical "set home to the root dir"
>> > default.  Sure, that might be an option.
>> 
>> If you mean "complain and set home to the root", then I'm happy with this
>> solution.

> No complain.  You still seem to have a problem to understand that this
> is underlying functionality under a couple of system calls generating
> passwd entries for arbitrary accounts.

> It's *not* necessarily the current account.  A user visible complaint for
> every unconfigured account enumerated via getpwent is quite over the top.

No, I perfectly understand it. The sooner I get slapped in the face with
a printout of my incorrect and intolerable settings, the better.

I do understand, that the settings MUST provide at least one sensible result.
Assuming we get sensible defaults, this will not be an issue for majority of
people.
However, for those, who wish to alter the setting, it is better, if they get a
slap this instant, if the setting is not quite right, rather than if they
discover issue after a long time is passed.
Issues with core configuration should not be masked by obscure defaults. IMHO.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 05.12.2014, <21:41>

Sorry for my terrible english...


--
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

