Received: (qmail 86474 invoked by uid 501); 27 Apr 2000 20:38:46 -0000 Message-Id: <20000427203846.86473.qmail@locus.apache.org> Date: 27 Apr 2000 20:38:46 -0000 From: Mitch C Reply-To: mitch@econquest.com To: submit@bugz.apache.org Subject: changes to UserDir permissions require restart to take effect X-Send-Pr-Version: 3.110 >Number: 6031 >Category: mod_userdir >Synopsis: changes to UserDir permissions require restart to take effect >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Apr 27 13:40:00 PDT 2000 >Closed-Date: Fri Sep 15 13:24:58 PDT 2000 >Last-Modified: Fri Sep 15 14:20:01 PDT 2000 >Originator: mitch@econquest.com >Release: 1.3.12 >Organization: >Environment: Linux xxx.domain.com 2.2.12-20smp #1 SMP Mon Sep 27 10:34:45 EDT 1999 i686 unknown >Description: If the user directory permissions are to restrictive to allow the apache user access to the "public_html" directory, once fixed apache must be restarted. >How-To-Repeat: chmod 700 ~user attempt to access user dir chmod 777 ~user chmod 777 ~user/publich_html access will still fail restart and access will be granted >Fix: Add this to the documentation of UserDir or timeout the cached results >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: slive State-Changed-When: Fri Sep 15 13:24:58 PDT 2000 State-Changed-Why: I think you missed something else here. This works fine for me without a restart. Thanks for using Apache. From: "Mitch \(eConquest\)" To: Cc: Subject: RE: mod_userdir/6031: changes to UserDir permissions require restart to take effect Date: Fri, 15 Sep 2000 14:11:10 -0700 I'm VERY careful about these things... Could there be difference caused by different platforms etc? At the time I was using Mandrake 6.1 - I don't have that around any more but I can attempt to verify again on my current systems. Again for clarity, say userdir was: drwx------ mike with or course a "public_html" under it with the same permissions, then the first attempt to access would of course be denied. Changing permissions to: drwxr-xr-x mike and of course to the sub-dir public_html DID NOT make them immediately accessible. Restarting the server did. Is there some kind of caching mechanism which would "remember" that the directory was unavailable? Or could that have been an OS "feature"? Thanks, Mitch -----Original Message----- From: slive@apache.org [mailto:slive@apache.org] Sent: Friday, September 15, 2000 1:25 PM To: apache-bugdb@apache.org; mitch@econquest.com; slive@apache.org Subject: Re: mod_userdir/6031: changes to UserDir permissions require restart to take effect [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ] Synopsis: changes to UserDir permissions require restart to take effect State-Changed-From-To: open-closed State-Changed-By: slive State-Changed-When: Fri Sep 15 13:24:58 PDT 2000 State-Changed-Why: I think you missed something else here. This works fine for me without a restart. Thanks for using Apache. From: Joshua Slive To: "Mitch (eConquest)" Cc: apbugs@apache.org Subject: RE: mod_userdir/6031: changes to UserDir permissions require restart to take effect Date: Fri, 15 Sep 2000 14:16:30 -0700 (PDT) On Fri, 15 Sep 2000, Mitch (eConquest) wrote: > I'm VERY careful about these things... > > Could there be difference caused by different platforms etc? At the time I > was using Mandrake 6.1 - I don't have that around any more but I can attempt > to verify again on my current systems. [...] > Is there some kind of caching mechanism which would "remember" that the > directory was unavailable? Or could that have been an OS "feature"? I really can't think of any reason that this would happen. Perhaps you had a badly behaving browser caching the error page? Apache does not do any cacheing unless you are accessing through the proxy module. If you can recreate it, I would be interested in the details. >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]