general/6814: setgid

[MARCO SALDARRIAGA <ma...@saldarriaga.net>]

>Number:         6814
>Category:       general
>Synopsis:       setgid
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Nov 07 17:40:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     marco@saldarriaga.net
>Release:        1.3.14
>Organization:
apache
>Environment:
Linux 2.2.17
>Description:
I was going to report a problem about setgid, but, of course, I decided to search the bug database first.

I found several people reporting the same problem, but at the bottom of each message I could see: >fix:, but the fix was not there.

I had to go to several messages until I found the solution in one of them; Now I have my server running.

What I want to report is that the bugs database should be more explicit with the fixes; it will save time to you and the users.

Just my 2 cents.  :-)

Marco
>How-To-Repeat:

>Fix:
Fixes easy to read and understand.
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> 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!     ]