From owner-freebsd-questions@FreeBSD.ORG Sun Aug 3 14:03:37 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5B82DD2 for ; Sun, 3 Aug 2014 14:03:37 +0000 (UTC) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A114E21F1 for ; Sun, 3 Aug 2014 14:03:37 +0000 (UTC) Received: from [192.168.0.4] (rbn1-216-180-76-216.adsl.hiwaay.net [216.180.76.216]) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id s73E3aar021853 for ; Sun, 3 Aug 2014 09:03:36 -0500 Message-ID: <53DE42AF.9030601@hiwaay.net> Date: Sun, 03 Aug 2014 09:09:51 -0500 From: "William A. Mahaffey III" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: "FreeBSD Questions !!!!" Subject: Re: permission problems w/ ordinary user .... References: <53DD742F.3020408@hiwaay.net> <20140803014039.75f4b2f9.freebsd@edvax.de> <53DD7AAD.4000902@hiwaay.net> <20140803020106.9696cf18.freebsd@edvax.de> <53DE32A3.3010606@hiwaay.net> <20140803135137.GA67311@slackbox.erewhon.home> In-Reply-To: <20140803135137.GA67311@slackbox.erewhon.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Aug 2014 14:03:37 -0000 On 08/03/14 08:51, Roland Smith wrote: > On Sun, Aug 03, 2014 at 08:01:23AM -0500, William A. Mahaffey III wrote: >>>> I have reset the perms as root several times during >>>> this exercise, & they keep getting unset after the login failure .... >>> I'm not sure what part of the system could trigger that behavuiour, >>> it just sounds totally wrong... >>> >>> However, you could run truss on an login attempt to see what >>> the process does (invisibly), calling /bin/chmod via execve() >>> or by chmod() or popen(). >> >> I eventually noticed that the default ~/.login_conf had an entry, >> commented out. I uncommented it, reset the perms, logged in & out >> several times, & everything went AOK. > If you aren't using it, you can delete ~/.login_conf, then you'll get the > default from /etc/login.conf. > >> Noob observation: that entry should be uncommented from the factory :-) .... > I don't think so. The settings in ~/.login_conf are an override to those in > /etc/login.conf, so it shouldn't matter if it's empty. > > And this example (which comes from /usr/share/skel/dot.login_conf) sets your > charset to iso-8859-1 and language to German. That might not be what you > want... > > Roland Yeah, I reset it to 'en_EN' .... uncommenting that entry did seem to fix my problem, but who knows .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.