Erin, Without thinking too hard about what's going on since I don't admin apache, I'm wondering if your problem could not just be that '/etc/.profile' should really be called '/etc/profile' . I believe the convention is that these types of files are dotfiles in users' directories (so they won't have to see them without ls -a) but do not have dot prefix in /etc/ directory where they apply systemwide. However, maybe you just mistyped below and it really is correctly named on your system.
HTH, Daniel > Date: Tue, 5 Dec 2000 00:14:59 -0500 > From: Eireann Lewy <[EMAIL PROTECTED]> > To: debian-user@lists.debian.org > Subject: Debian apache woes > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > Okay. I am completely and utterly at a loss here. I feel as if someone > has stolen my brain because I should not be this stupid. I am, however, > a relative linux fledgling (I have been windows-free for about a year > and a half on the outside, and that's if I take out various pitfalls but > anyway...). > > I'm having the following problems: > 1) The worst: Despite having umask 022 in /etc/.profile and everyone's > personal .profiles, newly created directories are randomly getting bad > perms. This is bad because most of my users don't know what the hell > permissions are, having none (except in very limited cases) in windows. > I just taught my two main cronies about chmod 755 and 644 (for regular > web files), but this shit can't keep happening. (For FTPed files, I set > up a umask in the wu-ftpd ftpaccess file to set things at 644 which > seemed to work.) >
