You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by "Roger D.Pack" <ro...@juno.com> on 1999/01/21 21:05:58 UTC
os-windows/3741: custom install does not set up conf directory
>Number: 3741
>Category: os-windows
>Synopsis: custom install does not set up conf directory
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: change-request
>Submitter-Id: apache
>Arrival-Date: Thu Jan 21 12:10:01 PST 1999
>Last-Modified:
>Originator: roger.pack@juno.com
>Organization:
apache
>Release: 1.3.4
>Environment:
win95a with
>Description:
I believe if you install and choose "custom" it does not set up your /conf/*.*
files foryou. (httpd.conf, etc.)
Also I think it would be nice to put a link to kill (shutdown) the apache server
in the "Apache Web Server" start menu directory, and a shortcut to httpd.conf, as
well, to make it easier. Maybe a shortcut to a command prompt in the apache
directory, too? Gotta make it easy :-)
>How-To-Repeat:
install, choose custom, change the directory to something else, or another drive
(I am not sure if this last step is necessary), see what it does.
>Fix:
disable custom? Cut and paste some directions from normal to custom? Tell
people not to use custom (if it's true that custom works as described).
>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 leave the subject line UNCHANGED. This is not done]
[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! ]