From bf8ac7551058df22dd5eb712631d9e383fc587a5 Mon Sep 17 00:00:00 2001 From: "barnboy%trilobyte.net" <> Date: Wed, 22 Aug 2001 10:44:14 +0000 Subject: Big checkin of docs to resolve every known outstanding doc bug! Yay release. Still many things to fix. Aren't there always? --- docs/html/win32.html | 358 ++++++++++++++++++++------------------------------- 1 file changed, 143 insertions(+), 215 deletions(-) (limited to 'docs/html/win32.html') diff --git a/docs/html/win32.html b/docs/html/win32.html index d0c1c8064..32f2515e8 100644 --- a/docs/html/win32.html +++ b/docs/html/win32.html @@ -126,7 +126,7 @@ VALIGN="TOP" of the Chapter 3Bugzilla Installation section while performing your Win32 installation.

very skilled Windows Systems - Administrator with both strong troubleshooting abilities and - a high tolerance for pain. Bugzilla on NT requires hacking - source code and implementing some advanced utilities. What - follows is the recommended installation procedure for Win32; - additional suggestions are provided in The Bugzilla FAQAppendix A.

Install Apache Web ServerApache Web + Server for Windows, and copy the Bugzilla files + somewhere Apache can serve them. Please follow all the + instructions referenced in Bugzilla Installation + regarding your Apache configuration, particularly + instructions regarding the "AddHandler" - for Windows. + parameter and "ExecCGI".

You may also use Internet Information Server or Personal Web - Server for this purpose. However, setup is slightly more - difficult. If ActivePerl doesn't seem to handle your file - associations correctly (for .cgi and .pl files), please - consult You may also use Internet Information Server or Personal + Web Server for this purpose. However, setup is quite + different. If ActivePerl doesn't seem to handle your + file associations correctly (for .cgi and .pl files), + please consult The Bugzilla FAQAppendix A.

"my $webservergid = getgrnam($my_webservergroup); " +> 
my $webservergid = getgrnam($my_webservergroup);
+

to

"my $webservergid = $my_webservergroup; " +> 
my $webservergid = $my_webservergroup;
+
+or the name of the group you wish to own the files explicitly: + 
my $webservergid = 'Administrators'
+

  • The code above needs testing as well to make sure it is correct.

    Some have found success using the commercial product, + Windmail. + You could try replacing your sendmail calls with: + 
    open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
+
    + or something to that effect. +

    This step is completely optional if you are using IIS or - another web server which only decides on an interpreter - based upon the file extension (.pl), rather than the +> This step is optional if you are using IIS or another + web server which only decides on an interpreter based + upon the file extension (.pl), rather than the "shebang"

    If you are using IIS 5.0 or higher, you must add cgi +> If you are using IIS or Personal Web Server, you must add cgi relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), - such as:

    From Andrew Pearson:

    "You can make Bugzilla work with Personal Web Server for - Windows 98 and higher, as well as for IIS 4.0. Microsoft has - information available at - You can make Bugzilla work with Personal Web Server for + Windows 98 and higher, as well as for IIS 4.0. + Microsoft has information available at http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP

    "Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:

    Hi - I am updating bugzilla to 2.12 so I can tell you what I did (after I - deleted the current dir and copied the files in). -

    In checksetup.pl, I did the following... - 

    my $webservergid = getgrnam($my_webservergroup);
-

    to

    my $webservergid = 'Administrators'		
-

  • I then ran checksetup.pl -

  • I removed all the encrypt() -

    If attempting to run Bugzilla 2.12 or older, you will need + to remove encrypt() calls from the Perl source. This is + not necessary for Bugzilla 2.13 and + later. +

    Example 3-4. Removing encrypt() for Windows NT installationsExample 3-4. Removing encrypt() for Windows NT Bugzilla version + 2.12 or earlier

    Replace this: - Replace this: + 
    SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
-    SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
-my $enteredcryptpwd = FetchOneColumn();
-
    +SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); +my $enteredcryptpwd = FetchOneColumn(); +
    - with this: - 
    my $enteredcryptpwd = $enteredpwd
-
    +my $enteredcryptpwd = $enteredpwd +
    - in cgi.pl. -

    -

  • I renamed processmail to processmail.pl -

  • I altered the sendmail statements to windmail: - 
      
-open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
-
    -

    The quotes around the dir is for the spaces. mail.log is for the output -

    • This was some late breaking information from Jan Evert. Sorry for the lack of formatting. -

    I'm busy installing bugzilla on a WinNT machine and I thought I'd notify you
    -at this moment of the commments I have to section 2.2.1 of the bugzilla
    -guide (at http://www.trilobyte.net/barnsons/html/).
    -
    -Step 1:
    -I've used apache, installation is really straightforward.
    -After reading the Unix installation instructions, I found that it is
    -necessary to add the ExecCGI option to the bugzilla directory. Also the
    -'AddHandler' line for .cgi is by default commented out.
    -
    -Step 3: although just a detail, 'ppm install <module%gt;' will also work
    -(without .ppd). And, it can also download these automatically from
    -ActiveState.
    -
    -Step 4: although I have cygwin installed, it seems that it is not necessary.
    -On my machine cygwin is not in the PATH and everything seems to work as
    -expected.
    -However, I've not used everything yet.
    -
    -Step 6: the 'bugs_password' given in SQL command d needs to be edited into
    -localconfig later on (Step 7) if the password is not empty. I've also edited
    -it into globals.pl, but I'm not sure that is needed. In both places, the
    -variable is named db_pass.
    -
    -Step 8: all the sendmail replacements mentioned are not as simple as
    -described there. Since I am not familiar (yet) with perl, I don't have any
    -mail working yet.
    -
    -Step 9: in globals.pl the encrypt() call can be replaced by just the
    -unencrypted password. In CGI.pl, the complete SQL command can be removed.
    -
    -Step 11: I've only changed the #! lines in *.cgi. I haven't noticed problems
    -with the system() call yet.
    -There seem to be only four system() called programs: processmail.pl (handled
    -by step 10), syncshadowdb (which should probably get the same treatment as
    -processmail.pl), diff and mysqldump. The last one is only needed with the
    -shadowdb feature (which I don't use).
    -
    -There seems to be one step missing: copying the bugzilla files somehwere
    -that apache can serve them.
    -
    -Just noticed the updated guide... Brian's comment is new. His first comment
    -will work, but opens up a huge security hole.