From owner-freebsd-questions Fri Nov 22 00:35:26 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA06023 for questions-outgoing; Fri, 22 Nov 1996 00:35:26 -0800 (PST) Received: from narcissus.ml.org (brosenga.st.pitzer.edu [134.173.120.201]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA06017 for ; Fri, 22 Nov 1996 00:35:22 -0800 (PST) Received: (from ben@localhost) by narcissus.ml.org (8.7.5/8.7.3) id AAA04370; Thu, 21 Nov 1996 00:38:44 -0800 (PST) Date: Thu, 21 Nov 1996 00:38:44 -0800 (PST) From: Snob Art Genre To: "Bryan K. Ogawa" cc: root@narcissus.ml.org, Snob Art Genre , questions@freebsd.org, JBH Subject: Re: tcsh apparently failing to run .cshrc In-Reply-To: <199611220810.AAA06313@foo.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 22 Nov 1996, Bryan K. Ogawa wrote: > In localhost.freebsd.questions you write: > > >On Fri, 22 Nov 1996, JBH wrote: > > [...] > > On the only account on which I was able to see this directly, > >there was an additional problem. I su'd to that account and found that I > >was unable to read or write its files! I logged in as root on another vty > > While there are a number of possible reasons for this, I'd check the > following things: > > 1. Is their home directory correctly specified in /etc/master.passwd > ? Yes. Adduser takes care of this. I used it to create all my users so if it were not doing this correctly I would have seen the problem sooner. > 2. Are their permissions set properly so that they can read their own > files, including .cshrc? This seems like it might be a problem, since > if root copies a file, the copy should be owned by root, but with > global read permissions. You might want to see if .cshrc is something > like mode 000 (no one can read it), since root will successfully > ignore this. Again, adduser does this. And I checked the permissions, too. > >and tried it again, and root could read and write the files with no > >problem. As root, I copied the .cshrc file for this account to a .tcshrc, > >and it ran on login as expected. I removed the .tcshrc and .cshrc still > >didn't work. > > -- > bryan k ogawa http://www.primenet.com/~bkogawa/ > I nuked the account in question and recreated it, and it works now, so this has become somewhat academic. I *would* like to know why it happened, in case it happens again, but it's not strictly necessary. Ben