diff options
| author | gerv%gerv.net <> | 2002-07-28 07:00:17 +0200 |
|---|---|---|
| committer | gerv%gerv.net <> | 2002-07-28 07:00:17 +0200 |
| commit | d8caf6045d10344c431918128e3803ca497565f3 (patch) | |
| tree | 1b2fbc50e442b6413a4ef0949e8ff7eed1df1361 /docs/html/win32.html | |
| parent | a9bb18746686c1bf5497e27f7ac2e12d0e3fc31a (diff) | |
| download | bugzilla-d8caf6045d10344c431918128e3803ca497565f3.tar.gz bugzilla-d8caf6045d10344c431918128e3803ca497565f3.tar.xz | |
Merging new docs from 2.16 branch.
Diffstat (limited to 'docs/html/win32.html')
| -rw-r--r-- | docs/html/win32.html | 1197 |
1 files changed, 644 insertions, 553 deletions
diff --git a/docs/html/win32.html b/docs/html/win32.html index 1a669f2b6..575bf8f4b 100644 --- a/docs/html/win32.html +++ b/docs/html/win32.html @@ -13,11 +13,11 @@ REL="UP" TITLE="Installation" HREF="installation.html"><LINK REL="PREVIOUS" -TITLE="Installation General Notes" -HREF="geninstall.html"><LINK +TITLE="Optional Additional Configuration" +HREF="extraconfig.html"><LINK REL="NEXT" -TITLE="Administering Bugzilla" -HREF="administration.html"></HEAD +TITLE="Mac OS X Installation Notes" +HREF="osx.html"></HEAD ><BODY CLASS="section" BGCOLOR="#FFFFFF" @@ -45,7 +45,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="geninstall.html" +HREF="extraconfig.html" ACCESSKEY="P" >Prev</A ></TD @@ -53,13 +53,13 @@ ACCESSKEY="P" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Chapter 3. Installation</TD +>Chapter 4. Installation</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="administration.html" +HREF="osx.html" ACCESSKEY="N" >Next</A ></TD @@ -73,33 +73,84 @@ CLASS="section" ><H1 CLASS="section" ><A -NAME="win32">3.6. Win32 Installation Notes</H1 -><P ->This section covers installation on Microsoft Windows 95, - 98, ME, NT, and 2000. Bugzilla works fine on Win32 platforms, - but please remember that the Bugzilla team and the author of the - Guide neither endorse nor support installation on Microsoft - Windows. Bugzilla installs and runs <EM ->best</EM -> - and <EM ->easiest</EM -> on UNIX-like operating systems, - and that is the way it will stay for the foreseeable future. The - Bugzilla team is considering supporting Win32 for the 2.16 - release and later.</P -><P ->The easiest way to install Bugzilla on Intel-archiecture - machines is to install some variant of GNU/Linux, then follow - the UNIX installation instructions in this Guide. If you have - any influence in the platform choice for running this system, - please choose GNU/Linux instead of Microsoft Windows.</P +NAME="win32">4.3. Win32 Installation Notes</H1 +><P +>This section covers installation on Microsoft Windows. + Bugzilla has been made to work on Win32 platforms, but the Bugzilla team + wish to emphasise that The easiest way to install Bugzilla on + Intel-archiecture machines + is to install some variant of GNU/Linux, then follow the UNIX + installation instructions in this Guide. If you have any influence in the + platform choice for running this system, please choose GNU/Linux instead + of Microsoft Windows.</P +><DIV +CLASS="warning" +><P +></P +><TABLE +CLASS="warning" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/warning.gif" +HSPACE="5" +ALT="Warning"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>After that warning, here's the situation for 2.16 + and Windows. It doesn't work at all out of the box. + You are almost certainly better off getting + the 2.17 version from CVS (after consultation with the Bugzilla Team to + make sure you are pulling on a stable day) because we'll be doing a load + of work to make the Win32 experience more pleasant than it is now. + </P +></TD +></TR +></TABLE +></DIV +><P +> If you still want to try this, to have any hope of getting it to work, + you'll need to apply the + <A +HREF="" +TARGET="_top" +>mail patch</A +> from + <A +HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=124174" +TARGET="_top" +>bug 124174</A +>. + After that, you'll need to read the (outdated) installation + instructions below, some (probably a lot better) <A +HREF="http://bugzilla.mozilla.org/attachment.cgi?id=84430&action=view" +TARGET="_top" +>more + recent ones</A +> kindly provided by Toms Baugis and Jean-Sebastien + Guay, and also check the + <A +HREF="http://www.bugzilla.org/releases/2.16/docs/win32.html" +TARGET="_top" +>Bugzilla 2.16 Win32 update page + </A +>. If we get time, + we'll write some better installation instructions for 2.16 and put + them up there. But no promises. + </P ><DIV CLASS="section" ><H2 CLASS="section" ><A -NAME="wininstall">3.6.1. Win32 Installation: Step-by-step</H2 +NAME="wininstall">4.3.1. Win32 Installation: Step-by-step</H2 ><DIV CLASS="note" ><P @@ -121,31 +172,33 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> You should be familiar with, and cross-reference, the rest - of the - <A +>You should be familiar with, and cross-reference, the rest of + the + <A HREF="installation.html" >Bugzilla Installation</A -> section while performing your - Win32 installation. - </P -><P -> Making Bugzilla work on Microsoft Windows is no - picnic. Support for Win32 has improved dramatically in the - last few releases, but, if you choose to proceed, you should - be a <EM +> + + section while performing your Win32 installation.</P +><P +>Making Bugzilla work on Microsoft Windows is no picnic. Support + for Win32 has improved dramatically in the last few releases, but, if + you choose to proceed, you should be a + <EM >very</EM -> skilled Windows Systems - Administrator with strong troubleshooting abilities, a high - tolerance for pain, and moderate perl skills. 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 - <A +> + + skilled Windows Systems Administrator with strong troubleshooting + abilities, a high tolerance for pain, and moderate perl skills. + 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 + <A HREF="faq.html" >Appendix A</A ->. - </P +> + + .</P ></TD ></TR ></TABLE @@ -156,27 +209,34 @@ CLASS="procedure" TYPE="1" ><LI ><P -> Install <A +>Install + <A HREF="http://www.apache.org/" TARGET="_top" ->Apache Web - Server</A -> for Windows, and copy the Bugzilla files - somewhere Apache can serve them. Please follow all the - instructions referenced in <A +>Apache Web Server</A +> + + for Windows, and copy the Bugzilla files somewhere Apache can serve + them. Please follow all the instructions referenced in + <A HREF="installation.html" >Bugzilla Installation</A > - regarding your Apache configuration, particularly - instructions regarding the <SPAN + + regarding your Apache configuration, particularly instructions + regarding the + <SPAN CLASS="QUOTE" >"AddHandler"</SPAN > - parameter and <SPAN + + parameter and + <SPAN CLASS="QUOTE" >"ExecCGI"</SPAN ->. - </P +> + + .</P ><DIV CLASS="note" ><P @@ -198,20 +258,20 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> 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 <A +>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 + <A HREF="faq.html" >Appendix A</A ->. - </P +> + + .</P ><P -> If you are going to use IIS, if on Windows NT you must - be updated to at least Service Pack 4. Windows 2000 - ships with a sufficient version of IIS. - </P +>If you are going to use IIS, if on Windows NT you must be + updated to at least Service Pack 4. Windows 2000 ships with a + sufficient version of IIS.</P ></TD ></TR ></TABLE @@ -219,46 +279,54 @@ HREF="faq.html" ></LI ><LI ><P -> Install <A +>Install + <A HREF="http://www.activestate.com/" TARGET="_top" >ActivePerl</A -> for Windows. Check <A +> + + for Windows. Check + <A HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/" TARGET="_top" ->http://aspn.activestate.com/ASPN/Downloads/ActivePerl</A -> for a current compiled binary. - </P +> http://aspn.activestate.com/ASPN/Downloads/ActivePerl</A +> + + for a current compiled binary.</P ><P -> Please also check the following links to fully understand the status - of ActivePerl on Win32: - <A +>Please also check the following links to fully understand the + status of ActivePerl on Win32: + <A HREF="http://language.perl.com/newdocs/pod/perlport.html" TARGET="_top" -> Perl Porting</A ->, and - <A +> Perl Porting</A +> + + , and + <A HREF="http://ftp.univie.ac.at/packages/perl/ports/nt/FAQ/perlwin32faq5.html" TARGET="_top" -> Perl on Win32 FAQ</A +> Perl on Win32 FAQ</A > - </P + </P ></LI ><LI ><P -> Use ppm from your perl\bin directory to install the following - packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, - GD, AppConfig, and Template. You may need to extract them from - .zip format using Winzip or other unzip program first. Most of - these additional ppm modules can be downloaded from ActiveState, - but AppConfig and Template should be obtained from OpenInteract - using <A +>Use ppm from your perl\bin directory to install the following + packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD, + AppConfig, and Template. You may need to extract them from .zip + format using Winzip or other unzip program first. Most of these + additional ppm modules can be downloaded from ActiveState, but + AppConfig and Template should be obtained from OpenInteract using + <A HREF="http://openinteract.sourceforge.net/" TARGET="_top" ->the instructions on - the Template Toolkit web site</A ->. - </P +>the + instructions on the Template Toolkit web site</A +> + + .</P ><DIV CLASS="note" ><P @@ -280,116 +348,129 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> You can find a list of modules at - <A +>You can find a list of modules at + <A HREF="http://www.activestate.com/PPMPackages/zips/5xx-builds-only" TARGET="_top" -> http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A +> http://www.activestate.com/PPMPackages/zips/5xx-builds-only/</A > - or <A + + or + <A HREF="http://www.activestate.com/PPMPackages/5.6plus" TARGET="_top" ->http://www.activestate.com/PPMPackages/5.6plus</A +> http://www.activestate.com/PPMPackages/5.6plus</A > - </P + </P ></TD ></TR ></TABLE ></DIV ><P -> The syntax for ppm is: - <TT +>The syntax for ppm is: + <TT CLASS="computeroutput" -> <TT +> <TT CLASS="prompt" ->C:> </TT -><B +>C:></TT +> + + <B CLASS="command" >ppm <modulename></B > - </TT + </TT > - </P + </P ><DIV CLASS="example" ><A -NAME="AEN985"><P +NAME="AEN989"><P ><B ->Example 3-3. Installing ActivePerl ppd Modules on Microsoft Windows</B +>Example 4-1. Installing ActivePerl ppd Modules on Microsoft + Windows</B ></P ><P -><TT +> <TT CLASS="prompt" >C:></TT -><B +> + + <B CLASS="command" ->ppm - <TT +>ppm + <TT CLASS="option" >DBD-Mysql</TT -></B -></P +> + </B +> + </P ><P >Watch your capitalization!</P ></DIV ><P -> ActiveState's 5.6Plus directory also contains an AppConfig ppm, so - you might see the following error when trying to install the - version at OpenInteract: - </P +>ActiveState's 5.6Plus directory also contains an AppConfig + ppm, so you might see the following error when trying to install + the version at OpenInteract:</P ><P > <TT CLASS="computeroutput" -> Error installing package 'AppConfig': Read a PPD for - 'AppConfig', but it is not intended for this build of Perl - (MSWin32-x86-multi-thread) - </TT +>Error installing package 'AppConfig': Read a PPD + for 'AppConfig', but it is not intended for this build of Perl + (MSWin32-x86-multi-thread)</TT > - </P + </P ><P -> If so, download both <A +>If so, download both + <A HREF="http://openinteract.sourceforge.net/ppmpackages/AppConfig.tar.gz" TARGET="_top" ->the - tarball</A -> and <A +> the tarball</A +> + + and + <A HREF="http://openinteract.sourceforge.net/ppmpackages/AppConfig.ppd" TARGET="_top" ->the - ppd</A -> directly from OpenInteract, then run ppm from within - the same directory to which you downloaded those files and - install the package by referencing the ppd file explicitly via in - the install command, f.e.: - <DIV +> the ppd</A +> + + directly from OpenInteract, then run ppm from within the same + directory to which you downloaded those files and install the + package by referencing the ppd file explicitly via in the install + command, f.e.: + <DIV CLASS="example" ><A -NAME="AEN998"><P +NAME="AEN1002"><P ><B ->Example 3-4. Installing OpenInteract ppd Modules manually on Microsoft - Windows</B +>Example 4-2. Installing OpenInteract ppd Modules manually on Microsoft + Windows</B ></P ><P -> <TT +> <TT CLASS="computeroutput" -><B +> <B CLASS="command" ->install +>install <TT CLASS="filename" >C:\AppConfig.ppd</TT -></B -></TT > - </P + </B +> + </TT +> + </P ></DIV > </P ></LI ><LI ><P -> Install MySQL for NT. - <DIV +>Install MySQL for NT. + <DIV CLASS="note" ><P ></P @@ -410,193 +491,211 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> You can download MySQL for Windows NT from <A +>You can download MySQL for Windows NT from + <A HREF="http://www.mysql.com/" TARGET="_top" >MySQL.com</A ->. Some find it helpful to use the WinMySqlAdmin utility, included with the download, to set up the database. - </P +> + + . Some find it helpful to use the WinMySqlAdmin utility, included + with the download, to set up the database.</P ></TD ></TR ></TABLE ></DIV > - </P + </P ></LI ><LI ><P -> Setup MySQL - </P +>Setup MySQL</P ><OL CLASS="SUBSTEPS" TYPE="a" ><LI ><P -> <TT +> <TT CLASS="computeroutput" -> <TT +> <TT CLASS="prompt" ->C:> </TT +>C:></TT > - <B + + <B CLASS="command" >C:\mysql\bin\mysql -u root mysql</B > - </TT + </TT > - </P + </P ></LI ><LI ><P -> <TT +> <TT CLASS="computeroutput" -> <TT +> <TT CLASS="prompt" >mysql></TT > - <B + + <B CLASS="command" ->DELETE FROM user WHERE Host='localhost' AND User='';</B +>DELETE FROM user WHERE Host='localhost' AND + User='';</B > - </TT + </TT > - </P + </P ></LI ><LI ><P -> <TT +> <TT CLASS="computeroutput" -> <TT +> <TT CLASS="prompt" >mysql></TT > - <B + + <B CLASS="command" >UPDATE user SET Password=PASSWORD ('new_password') - WHERE user='root';</B + WHERE user='root';</B > - </TT + </TT > - </P + </P ><P -><SPAN +> <SPAN CLASS="QUOTE" >"new_password"</SPAN ->, above, indicates - whatever password you wish to use for your - <SPAN +> + + , above, indicates whatever password you wish to use for your + <SPAN CLASS="QUOTE" >"root"</SPAN -> user.</P +> + + user.</P ></LI ><LI ><A NAME="ntbugs-password" ></A ><P -> <TT +> <TT CLASS="computeroutput" -> <TT +> <TT CLASS="prompt" >mysql></TT > - <B + + <B CLASS="command" ->GRANT SELECT, INSERT, UPDATE, DELETE, - INDEX, ALTER, CREATE, DROP, REFERENCES - ON bugs.* to bugs@localhost - IDENTIFIED BY 'bugs_password';</B +>GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, + ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost + IDENTIFIED BY 'bugs_password';</B > - </TT + </TT > - </P + </P ><P -><SPAN +> <SPAN CLASS="QUOTE" >"bugs_password"</SPAN ->, above, indicates - whatever password you wish to use for your - <SPAN +> + + , above, indicates whatever password you wish to use for your + <SPAN CLASS="QUOTE" >"bugs"</SPAN -> user.</P +> + + user.</P ></LI ><LI ><P -> <TT +> <TT CLASS="computeroutput" -> <TT +> <TT CLASS="prompt" >mysql></TT > - <B + + <B CLASS="command" >FLUSH PRIVILEGES;</B > - </TT + </TT > - </P + </P ></LI ><LI ><P -> <TT +> <TT CLASS="computeroutput" -> <TT +> <TT CLASS="prompt" >mysql></TT > - <B + + <B CLASS="command" >create database bugs;</B > - </TT + </TT > - </P + </P ></LI ><LI ><P -> <TT +> <TT CLASS="computeroutput" -> <TT +> <TT CLASS="prompt" >mysql></TT > - <B + + <B CLASS="command" >exit;</B > - </TT + </TT > - </P + </P ></LI ><LI ><P -> <TT +> <TT CLASS="computeroutput" -> <TT +> <TT CLASS="prompt" >C:></TT > - <B + + <B CLASS="command" ->C:\mysql\bin\mysqladmin -u root -p reload</B +>C:\mysql\bin\mysqladmin -u root -p + reload</B > - </TT + </TT > - </P + </P ></LI ></OL ></LI ><LI ><P -> Edit <TT +>Edit + <TT CLASS="filename" >checksetup.pl</TT -> in your Bugzilla directory. Change - this line: - </P +> + + in your Bugzilla directory. Change this line:</P ><P -> <TABLE +> <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -606,19 +705,18 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> my $webservergid = getgrnam($my_webservergroup); - </PRE +>my $webservergid = + getgrnam($my_webservergroup);</PRE ></FONT ></TD ></TR ></TABLE > - </P + </P ><P -> to - </P +>to</P ><P -> <TABLE +> <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -628,15 +726,16 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> my $webservergid = $my_webservergroup; - </PRE +>my $webservergid = + $my_webservergroup;</PRE ></FONT ></TD ></TR ></TABLE > -or the name of the group you wish to own the files explicitly: - <TABLE + + or the name of the group you wish to own the files explicitly: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -646,46 +745,64 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> my $webservergid = 'Administrators' - </PRE +>my $webservergid = + 'Administrators'</PRE ></FONT ></TD ></TR ></TABLE > - </P + </P ></LI ><LI ><P -> Run <TT +>Run + <TT CLASS="filename" >checksetup.pl</TT -> from the Bugzilla directory. - </P +> + + from the Bugzilla directory.</P ></LI ><LI ><P ->Edit <TT +>Edit + <TT CLASS="filename" >localconfig</TT -> to suit your - requirements. Set <TT +> + + to suit your requirements. Set + <TT CLASS="varname" >$db_pass</TT -> to your - <SPAN +> + + to your + <SPAN CLASS="QUOTE" >"bugs_password"</SPAN -> from <A +> + + from + <A HREF="win32.html#ntbugs-password" >step 5.d</A ->, and <TT +> + + , and + <TT CLASS="varname" >$webservergroup</TT -> to <SPAN +> + + to + <SPAN CLASS="QUOTE" >"8"</SPAN ->.</P +> + + .</P ><DIV CLASS="note" ><P @@ -707,15 +824,19 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->Not sure on the <SPAN +>Not sure on the + <SPAN CLASS="QUOTE" >"8"</SPAN -> for - <TT +> + + for + <TT CLASS="varname" >$webservergroup</TT -> above. If it's - wrong, please send corrections.</P +> + + above. If it's wrong, please send corrections.</P ></TD ></TR ></TABLE @@ -723,21 +844,24 @@ CLASS="varname" ></LI ><LI ><P -> Edit <TT +>Edit + <TT CLASS="filename" >defparams.pl</TT -> to suit your - requirements. Particularly, set - <TT +> + + to suit your requirements. Particularly, set + <TT CLASS="varname" >DefParam("maintainer")</TT -> and - <TT +> + + and + <TT CLASS="varname" ->DefParam("urlbase") to match your - install.</TT +>DefParam("urlbase") to match your install.</TT > - </P + </P ><DIV CLASS="note" ><P @@ -760,9 +884,9 @@ ALIGN="LEFT" VALIGN="TOP" ><P >This is yet another step I'm not sure of, since the - maintainer of this documentation does not maintain - Bugzilla on NT. If you can confirm or deny that this - step is required, please let me know.</P + maintainer of this documentation does not maintain Bugzilla on + NT. If you can confirm or deny that this step is required, please + let me know.</P ></TD ></TR ></TABLE @@ -790,30 +914,38 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> There are several alternatives to Sendmail that will work on Win32. - The one mentioned here is a <EM +>There are several alternatives to Sendmail that will work + on Win32. The one mentioned here is a + <EM >suggestion</EM ->, not - a requirement. Some other mail packages that can work include - <A +> + + , not a requirement. Some other mail packages that can work + include + <A HREF="http://www.blat.net/" TARGET="_top" >BLAT</A ->, - <A +> + + , + <A HREF="http://www.geocel.com/windmail/" TARGET="_top" >Windmail</A ->, - <A +> + + , + <A HREF="http://www.dynamicstate.com/" TARGET="_top" ->Mercury Sendmail</A ->, - and the CPAN Net::SMTP Perl module (available in .ppm). - Every option requires some hacking of the Perl scripts for Bugzilla - to make it work. The option here simply requires the least. - </P +>Mercury + Sendmail</A +> + + , and the CPAN Net::SMTP Perl module (available in .ppm). Every + option requires some hacking of the Perl scripts for Bugzilla to + make it work. The option here simply requires the least.</P ></TD ></TR ></TABLE @@ -824,12 +956,16 @@ CLASS="procedure" TYPE="1" ><LI ><P -> Download NTsendmail, available from<A +>Download NTsendmail, available from + <A HREF="http://www.ntsendmail.com/" TARGET="_top" -> www.ntsendmail.com</A ->. You must have a "real" mail server which allows you to relay off it in your $ENV{"NTsendmail"} (which you should probably place in globals.pl) - </P +> www.ntsendmail.com</A +> + + . You must have a "real" mail server which allows you to relay + off it in your $ENV{"NTsendmail"} (which you should probably + place in globals.pl)</P ></LI ><LI ><P @@ -848,12 +984,11 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> # these settings configure the NTsendmail process -use NTsendmail; -$ENV{"NTsendmail"}="your.smtpserver.box"; -$ENV{"NTsendmail_debug"}=1; -$ENV{"NTsendmail_max_tries"}=5; - </PRE +># these settings configure the NTsendmail + process use NTsendmail; + $ENV{"NTsendmail"}="your.smtpserver.box"; + $ENV{"NTsendmail_debug"}=1; + $ENV{"NTsendmail_max_tries"}=5;</PRE ></FONT ></TD ></TR @@ -879,28 +1014,34 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> Some mention to also edit - <TT +>Some mention to also edit + <TT CLASS="varname" >$db_pass</TT -> in - <TT +> + + in + <TT CLASS="filename" >globals.pl</TT -> to be your - <SPAN +> + + to be your + <SPAN CLASS="QUOTE" >"bugs_password"</SPAN ->. Although this may get - you around some problem authenticating to your - database, since globals.pl is not normally - restricted by <TT +> + + . Although this may get you around some problem + authenticating to your database, since globals.pl is not + normally restricted by + <TT CLASS="filename" >.htaccess</TT ->, your - database password is exposed to whoever uses your - web server. - </P +> + + , your database password is exposed to whoever uses your web + server.</P ></TD ></TR ></TABLE @@ -908,16 +1049,19 @@ CLASS="filename" ></LI ><LI ><P -> Find and comment out all occurences of - <SPAN +>Find and comment out all occurences of + <SPAN CLASS="QUOTE" ->"<B +>" + <B CLASS="command" >open(SENDMAIL</B ->"</SPAN -> in - your Bugzilla directory. Then replace them with: - <TABLE +> + "</SPAN +> + + in your Bugzilla directory. Then replace them with: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -927,19 +1071,16 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> # new sendmail functionality -my $mail=new NTsendmail; -my $from="bugzilla\@your.machine.name.tld"; -my $to=$login; -my $subject=$urlbase; -$mail->send($from,$to,$subject,$msg); - </PRE +># new sendmail functionality my $mail=new + NTsendmail; my $from="bugzilla\@your.machine.name.tld"; my + $to=$login; my $subject=$urlbase; + $mail->send($from,$to,$subject,$msg);</PRE ></FONT ></TD ></TR ></TABLE > - </P + </P ><DIV CLASS="note" ><P @@ -961,13 +1102,14 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> Some have found success using the commercial product, - <SPAN +>Some have found success using the commercial product, + <SPAN CLASS="productname" >Windmail</SPAN ->. - You could try replacing your sendmail calls with: - <TABLE +> + + . You could try replacing your sendmail calls with: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -977,15 +1119,16 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log"; - </PRE +>open SENDMAIL, + "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > + mail.log";</PRE ></FONT ></TD ></TR ></TABLE > - or something to that effect. - </P + + or something to that effect.</P ></TD ></TR ></TABLE @@ -996,24 +1139,31 @@ CLASS="programlisting" ></LI ><LI ><P -> Change all references in all files from - <TT +>Change all references in all files from + <TT CLASS="filename" >processmail</TT -> to - <TT +> + + to + <TT CLASS="filename" >processmail.pl</TT ->, and - rename <TT +> + + , and rename + <TT CLASS="filename" >processmail</TT -> to - <TT +> + + to + <TT CLASS="filename" >processmail.pl</TT ->. - </P +> + + .</P ><DIV CLASS="note" ><P @@ -1035,10 +1185,9 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> Many think this may be a change we want to make for - main-tree Bugzilla. It's painless for the UNIX folks, - and will make the Win32 people happier. - </P +>Many think this may be a change we want to make for + main-tree Bugzilla. It's painless for the UNIX folks, and will + make the Win32 people happier.</P ></TD ></TR ></TABLE @@ -1064,8 +1213,10 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> Some people have suggested using the Net::SMTP Perl module instead of NTsendmail or the other options listed here. You can change processmail.pl to make this work. - <TABLE +>Some people have suggested using the Net::SMTP Perl module + instead of NTsendmail or the other options listed here. You can + change processmail.pl to make this work. + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1088,14 +1239,15 @@ $logstr = "$logstr; mail sent to $tolist $cclist"; } -</PRE + </PRE ></FONT ></TD ></TR ></TABLE > -here is a test mail program for Net::SMTP: -<TABLE + + here is a test mail program for Net::SMTP: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1122,13 +1274,13 @@ recipient's address exit; -</PRE + </PRE ></FONT ></TD ></TR ></TABLE > - </P + </P ></TD ></TR ></TABLE @@ -1156,50 +1308,58 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> 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 - <SPAN +>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 + <SPAN CLASS="QUOTE" >"shebang"</SPAN -> line (#/usr/bonsaitools/bin/perl) - </P +> + + line (#/usr/bonsaitools/bin/perl)</P ></TD ></TR ></TABLE ></DIV ><P -> Modify the path to perl on the first line (#!) of all - files to point to your Perl installation, and add - <SPAN +>Modify the path to perl on the first line (#!) of all files + to point to your Perl installation, and add + <SPAN CLASS="QUOTE" >"perl"</SPAN -> to the beginning of all Perl system - calls that use a perl script as an argument. This may - take you a while. There is a <SPAN +> + + to the beginning of all Perl system calls that use a perl script as + an argument. This may take you a while. There is a + <SPAN CLASS="QUOTE" >"setperl.csh"</SPAN > - utility to speed part of this procedure, available in the - <A + + utility to speed part of this procedure, available in the + <A HREF="patches.html" >Useful Patches and Utilities for Bugzilla</A -> section of The Bugzilla Guide. - However, it requires the Cygwin GNU-compatible environment - for Win32 be set up in order to work. See <A +> + + section of The Bugzilla Guide. However, it requires the Cygwin + GNU-compatible environment for Win32 be set up in order to work. + See + <A HREF="http://www.cygwin.com/" TARGET="_top" >http://www.cygwin.com/</A -> for details on obtaining Cygwin. - </P +> + + for details on obtaining Cygwin.</P ></LI ><LI ><P -> Modify the invocation of all system() calls in all perl - scripts in your Bugzilla directory. You should specify the - full path to perl for each system() call. For instance, change - this line in processmail: - <TABLE +>Modify the invocation of all system() calls in all perl + scripts in your Bugzilla directory. You should specify the full + path to perl for each system() call. For instance, change this line + in processmail: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1209,50 +1369,61 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> +> system ("./processmail",@ARGLIST); - </programlisting> to - <programlisting> + </programlisting> to + <programlisting> system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST); - </PRE + + </PRE ></FONT ></TD ></TR ></TABLE > - </P + </P ></LI ><LI ><P -> Add <TT +>Add + <TT CLASS="function" >binmode()</TT -> calls so attachments - will work (<A +> + + calls so attachments will work ( + <A HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000" TARGET="_top" ->bug 62000</A ->). - </P +>bug + 62000</A +> + + ).</P ><P -> Because Microsoft Windows based systems handle binary - files different than Unix based systems, you need to add - the following lines to - <TT +>Because Microsoft Windows based systems handle binary files + different than Unix based systems, you need to add the following + lines to + <TT CLASS="filename" >createattachment.cgi</TT -> and - <TT +> + + and + <TT CLASS="filename" >showattachment.cgi</TT -> before the - <TT +> + + before the + <TT CLASS="function" >require 'CGI.pl';</TT -> line. -</P +> + + line.</P ><P -> <TABLE +> <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1266,7 +1437,7 @@ CLASS="programlisting" binmode(STDIN); binmode(STDOUT); -</PRE + </PRE ></FONT ></TD ></TR @@ -1294,28 +1465,35 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> According to <A +>According to + <A HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=62000" TARGET="_top" ->bug 62000</A ->, - the perl documentation says that you should always use - <TT +> bug 62000</A +> + + , the perl documentation says that you should always use + <TT CLASS="function" >binmode()</TT -> when dealing with binary - files, but never when dealing with text files. That seems - to suggest that rather than arbitrarily putting - <TT +> + + when dealing with binary files, but never when dealing with text + files. That seems to suggest that rather than arbitrarily putting + + <TT CLASS="function" >binmode()</TT -> at the beginning of the - attachment files, there should be logic to determine if - <TT +> + + at the beginning of the attachment files, there should be logic + to determine if + <TT CLASS="function" >binmode()</TT -> is needed or not. - </P +> + + is needed or not.</P ></TD ></TR ></TABLE @@ -1344,13 +1522,12 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> 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: - </P +>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:</P ><P -> <TABLE +> <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1360,19 +1537,16 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> -.cgi to: <perl install directory>\perl.exe %s %s -.pl to: <perl install directory>\perl.exe %s %s -GET,HEAD,POST - </PRE +>.cgi to: <perl install directory>\perl.exe %s + %s .pl to: <perl install directory>\perl.exe %s %s + GET,HEAD,POST</PRE ></FONT ></TD ></TR ></TABLE -> - Change the path to Perl to match your - install, of course. - </P +> + + Change the path to Perl to match your install, of course.</P ></TD ></TR ></TABLE @@ -1383,7 +1557,7 @@ CLASS="section" ><H2 CLASS="section" ><A -NAME="addlwintips">3.6.2. Additional Windows Tips</H2 +NAME="addlwintips">4.3.2. Additional Windows Tips</H2 ><DIV CLASS="tip" ><P @@ -1405,25 +1579,25 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> From Andrew Pearson: - <A -NAME="AEN1168"><BLOCKQUOTE +>From Andrew Pearson: + <A +NAME="AEN1172"><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> 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 <A -HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP" +>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 + <A +HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP" TARGET="_top" -> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A +> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A > - </P + </P ><P -> Basically you need to add two String Keys in the - registry at the following location: - </P +>Basically you need to add two String Keys in the registry at + the following location:</P ><P -> <TABLE +> <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1433,29 +1607,27 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap - </PRE +> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap</PRE ></FONT ></TD ></TR ></TABLE > - </P + </P ><P -> The keys should be called ".pl" and ".cgi", and both - should have a value something like: - <B +>The keys should be called ".pl" and ".cgi", and both should + have a value something like: + <B CLASS="command" >c:/perl/bin/perl.exe "%s" "%s"</B > - </P + </P ><P -> The KB article only talks about .pl, but it goes into - more detail and provides a perl test script. - </P +>The KB article only talks about .pl, but it goes into more + detail and provides a perl test script.</P ></BLOCKQUOTE > - </P + </P ></TD ></TR ></TABLE @@ -1481,24 +1653,25 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> If attempting to run Bugzilla 2.12 or older, you will need - to remove encrypt() calls from the Perl source. This is - <EM +>If attempting to run Bugzilla 2.12 or older, you will need to + remove encrypt() calls from the Perl source. This is + <EM >not necessary</EM -> for Bugzilla 2.13 and - later, which includes the current release, Bugzilla - 2.16. - <DIV +> + + for Bugzilla 2.13 and later, which includes the current release, + Bugzilla &bz-ver;. + <DIV CLASS="example" ><A -NAME="AEN1180"><P +NAME="AEN1184"><P ><B ->Example 3-5. Removing encrypt() for Windows NT Bugzilla version - 2.12 or earlier</B +>Example 4-3. Removing encrypt() for Windows NT Bugzilla version 2.12 or + earlier</B ></P ><P -> Replace this: - <TABLE +>Replace this: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1508,17 +1681,17 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> -SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); -my $enteredcryptpwd = FetchOneColumn(); - </PRE +>SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . + ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); my + $enteredcryptpwd = FetchOneColumn();</PRE ></FONT ></TD ></TR ></TABLE -> -with this: - <TABLE +> + + with this: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1528,104 +1701,22 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="programlisting" -> -my $enteredcryptpwd = $enteredpwd - </PRE +>my $enteredcryptpwd = $enteredpwd</PRE ></FONT ></TD ></TR ></TABLE -> - in cgi.pl. - </P +> + + in cgi.pl.</P ></DIV > - </P + </P ></TD ></TR ></TABLE ></DIV ></DIV -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="bzldap">3.6.3. Bugzilla LDAP Integration</H2 -><P -> What follows is some late-breaking information on using the - LDAP authentication options with Bugzilla. The author has not - tested these (nor even formatted this section!) so please - contribute feedback to the newsgroup. - </P -><P -CLASS="literallayout" -><br> -Mozilla::LDAP module<br> -<br> -The Mozilla::LDAP module allows you to use LDAP for authentication to<br> -the Bugzilla system. This module is not required if you are not using<br> -LDAP.<br> -<br> -Mozilla::LDAP (aka PerLDAP) is available for download from<br> -http://www.mozilla.org/directory.<br> -<br> -NOTE: The Mozilla::LDAP module requires Netscape's Directory SDK.<br> -Follow the link for "Directory SDK for C" on that same page to<br> -download the SDK first. After you have installed this SDK, then<br> -install the PerLDAP module.<br> -----------------------------------------------------------------------<br> -<br> -Post-Installation Checklist<br> -----------------------------------------------------------------------<br> -Set useLDAP to "On" **only** if you will be using an LDAP directory<br> -for authentication. Be very careful when setting up this parameter;<br> -if you set LDAP authentication, but do not have a valid LDAP directory<br> -set up, you will not be able to log back in to Bugzilla once you log<br> -out. (If this happens, you can get back in by manually editing the<br> -data/params file, and setting useLDAP back to 0.)<br> -<br> -If using LDAP, you must set the three additional parameters:<br> -<br> -Set LDAPserver to the name (and optionally port) of your LDAP server.<br> -If no port is specified, it defaults to the default port of 389. (e.g<br> -"ldap.mycompany.com" or "ldap.mycompany.com:1234")<br> -<br> -Set LDAPBaseDN to the base DN for searching for users in your LDAP<br> -directory. (e.g. "ou=People,o=MyCompany") uids must be unique under<br> -the DN specified here.<br> -<br> -Set LDAPmailattribute to the name of the attribute in your LDAP<br> -directory which contains the primary email address. On most directory<br> -servers available, this is "mail", but you may need to change this.<br> -----------------------------------------------------------------------<br> -<br> -(Not sure where this bit should go, but it's important that it be in<br> -there somewhere...)<br> -----------------------------------------------------------------------<br> -Using LDAP authentication for Bugzilla:<br> -<br> -The existing authentication scheme for Bugzilla uses email addresses<br> -as the primary user ID, and a password to authenticate that user. All<br> -places within Bugzilla where you need to deal with user ID (e.g<br> -assigning a bug) use the email address.<br> -<br> -The LDAP authentication builds on top of this scheme, rather than<br> -replacing it. The initial log in is done with a username and password<br> -for the LDAP directory. This then fetches the email address from LDAP<br> -and authenticates seamlessly in the standard Bugzilla authentication<br> -scheme using this email address. If an account for this address<br> -already exists in your Bugzilla system, it will log in to that<br> -account. If no account for that email address exists, one is created<br> -at the time of login. (In this case, Bugzilla will attempt to use the<br> -"displayName" or "cn" attribute to determine the user's full name.)<br> -<br> -After authentication, all other user-related tasks are still handled<br> -by email address, not LDAP username. You still assign bugs by email<br> -address, query on users by email address, etc.<br> -----------------------------------------------------------------------<br> - </P -></DIV ></DIV ><DIV CLASS="NAVFOOTER" @@ -1643,7 +1734,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="geninstall.html" +HREF="extraconfig.html" ACCESSKEY="P" >Prev</A ></TD @@ -1661,7 +1752,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="administration.html" +HREF="osx.html" ACCESSKEY="N" >Next</A ></TD @@ -1671,7 +1762,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Installation General Notes</TD +>Optional Additional Configuration</TD ><TD WIDTH="34%" ALIGN="center" @@ -1685,7 +1776,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Administering Bugzilla</TD +>Mac OS X Installation Notes</TD ></TR ></TABLE ></DIV |