Skip to content

bugzilla
bugzilla
Switch branch/tag
Find file
BlameHistoryPermalink
stepbystep.html 40.2 KB
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 
<HTML
><HEAD
><TITLE
>Step-by-step Install</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Installation"
HREF="installation.html"><LINK
REL="PREVIOUS"
TITLE="ERRATA"
HREF="errata.html"><LINK
REL="NEXT"
TITLE="Mac OS X Installation Notes"
HREF="osx.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="errata.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Installation</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="osx.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="stepbystep">3.2. Step-by-step Install</H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN509">3.2.1. Introduction</H2
><P
>&#13;	Installation of bugzilla is pretty straightforward, particularly if your
	machine already has MySQL and the MySQL-related perl packages installed.
	If those aren't installed yet, then that's the first order of business.  The
	other necessary ingredient is a web server set up to run cgi scripts.
	While using Apache for your webserver is not required, it is recommended.
      </P
><P
>&#13;	Bugzilla has been successfully installed under Solaris, Linux,
	and Win32. The peculiarities of installing on Win32 (Microsoft
	Windows) are not included in this section of the Guide; please
	check out the <A
HREF="win32.html"
>Win32 Installation Notes</A
> for further advice
	on getting Bugzilla to work on Microsoft Windows.
      </P
><P
>&#13;	The Bugzilla Guide is contained in the "docs/" folder in your
	Bugzilla distribution.  It is available in plain text
	(docs/txt), HTML (docs/html), or SGML source (docs/sgml).
      </P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN515">3.2.2. Installing the Prerequisites</H2
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you want to skip these manual installation steps for
	  the CPAN dependencies listed below, and are running the very
	  most recent version of Perl and MySQL (both the executables
	  and development libraries) on your system, check out
	  Bundle::Bugzilla in <A
HREF="stepbystep.html#bundlebugzilla"
>Using Bundle::Bugzilla instead of manually installing Perl modules</A
></P
></TD
></TR
></TABLE
></DIV
><P
>&#13;	The software packages necessary for the proper running of bugzilla are:
	<P
></P
><OL
TYPE="1"
><LI
><P
>&#13;	      MySQL database server and the mysql client (3.22.5 or greater)
	    </P
></LI
><LI
><P
>&#13;	      Perl (5.004 or greater, 5.6.1 is recommended if you wish
	      to use Bundle::Bugzilla)
	    </P
></LI
><LI
><P
>&#13;	      DBI Perl module
	    </P
></LI
><LI
><P
>&#13;	      Data::Dumper Perl module
	    </P
></LI
><LI
><P
>&#13;	      Bundle::Mysql Perl module collection
	    </P
></LI
><LI
><P
>&#13;	      TimeDate Perl module collection
	    </P
></LI
><LI
><P
>&#13;	      GD perl module (1.8.3) (optional, for bug charting)
	    </P
></LI
><LI
><P
>&#13;	      Chart::Base Perl module (0.99c) (optional, for bug charting)
	    </P
></LI
><LI
><P
>&#13;	      DB_File Perl module (optional, for bug charting)
	    </P
></LI
><LI
><P
>&#13;	      The web server of your choice.  Apache is recommended.
	    </P
></LI
><LI
><P
>&#13;	      MIME::Parser Perl module (optional, for contrib/bug_email.pl interface)
	    </P
></LI
></OL
>

	<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
>&#13;	    It is a good idea, while installing Bugzilla, to ensure it
	    is not <EM
>accessible</EM
> by other machines
	    on the Internet. Your machine may be vulnerable to attacks
	    while you are installing. In other words, ensure there is
	    some kind of firewall between you and the rest of the
	    Internet.  Many installation steps require an active
	    Internet connection to complete, but you must take care to
	    ensure that at no point is your machine vulnerable to an
	    attack.
	  </P
></TD
></TR
></TABLE
></DIV
>
	<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Linux-Mandrake 8.0, the author's test system, includes
	    every required and optional library for Bugzilla.  The
	    easiest way to install them is by using the
	    <TT
CLASS="filename"
>urpmi</TT
> utility.  If you follow these
	    commands, you should have everything you need for
	    Bugzilla, and <TT
CLASS="filename"
>checksetup.pl</TT
> should
	    not complain about any missing libraries.  You may already
	    have some of these installed.</P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
><TT
CLASS="prompt"
>bash#</TT
><B
CLASS="command"
> urpmi
		perl-mysql</B
></TD
></TR
><TR
><TD
><TT
CLASS="prompt"
>bash#</TT
><B
CLASS="command"
> urpmi
		perl-chart</B
></TD
></TR
><TR
><TD
><TT
CLASS="prompt"
>bash#</TT
><B
CLASS="command"
> urpmi
		perl-gd</B
></TD
></TR
><TR
><TD
><TT
CLASS="prompt"
>bash#</TT
><B
CLASS="command"
> urpmi
		perl-MailTools</B
> (for Bugzilla email
	      integration)</TD
></TR
><TR
><TD
><TT
CLASS="prompt"
>bash#</TT
><B
CLASS="command"
> urpmi
		apache-modules</B
></TD
></TR
></TBODY
></TABLE
><P
></P
></TD
></TR
></TABLE
></DIV
>
	
      </P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="install-mysql">3.2.3. Installing MySQL Database</H2
><P
>&#13;	Visit MySQL homepage at <A
HREF="http://www.mysql.com"
TARGET="_top"
>www.mysql.com</A
> and grab the latest stable release of the server.  Many of the binary versions of MySQL store their data files in <TT
CLASS="filename"
>/var</TT
> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <TT
CLASS="filename"
>configure</TT
>.
      </P
><P
>&#13;	If you install from source or non-package (RPM, deb, etc.)
	binaries you need to add
	<I
CLASS="firstterm"
>mysqld</I
> to your
	init scripts so the server daemon will come back up whenever
	your machine reboots. Further discussion of UNIX init
	sequences are beyond the scope of this guide.
	<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You should have your init script start
	    <I
CLASS="glossterm"
>mysqld</I
> with the ability to accept
	    large packets. By default, <TT
CLASS="filename"
>mysqld</TT
>
	    only accepts packets up to 64K long. This limits the size
	    of attachments you may put on bugs. If you add <TT
CLASS="option"
>-O
	    max_allowed_packet=1M</TT
> to the command that starts
	    <TT
CLASS="filename"
>mysqld</TT
> (or
	    <TT
CLASS="filename"
>safe_mysqld</TT
>), then you will be able
	    to have attachments up to about 1 megabyte.</P
></TD
></TR
></TABLE
></DIV
>

      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;	  If you plan on running Bugzilla and MySQL on the same
	  machine, consider using the <TT
CLASS="option"
>--skip-networking</TT
>
	  option in the init script. This enhances security by
	  preventing network access to MySQL.
	</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="install-perl">3.2.4. Perl (5.004 or greater)</H2
><P
>&#13;	Any machine that doesn't have perl on it is a sad machine
	indeed.  Perl for *nix systems can be gotten in source form
	from http://www.perl.com.  Although Bugzilla runs with most
	post-5.004 versions of Perl, it's a good idea to be up to the
	very latest version if you can when running Bugzilla.  As of
	this writing, that is perl version 5.6.1.
      </P
><P
>&#13;	Perl is now a far cry from the the single compiler/interpreter
	binary it once was.  It includes a great many required modules
	and quite a few other support files.  If you're not up to or
	not inclined to build perl from source, you'll want to install
	it on your machine using some sort of packaging system (be it
	RPM, deb, or what have you) to ensure a sane install. In the
	subsequent sections you'll be installing quite a few perl
	modules; this can be quite ornery if your perl installation
	isn't up to snuff.
      </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
>Many people complain that Perl modules will not install
	  for them.  Most times, the error messages complain that they
	  are missing a file in <SPAN
CLASS="QUOTE"
>"@INC"</SPAN
>.  Virtually every
	  time, this is due to permissions being set too restrictively
	  for you to compile Perl modules or not having the necessary
	  Perl development libraries installed on your system..
	  Consult your local UNIX systems administrator for help
	  solving these permissions issues; if you
	  <EM
>are</EM
> the local UNIX sysadmin, please
	  consult the newsgroup/mailing list for further assistance or
	  hire someone to help you out.
	</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="tip"
><A
NAME="bundlebugzilla"><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;	  You can skip the following Perl module installation steps by
	  installing <SPAN
CLASS="productname"
>Bundle::Bugzilla</SPAN
> from
	  <A
HREF="glossary.html#gloss-cpan"
><I
CLASS="glossterm"
>CPAN</I
></A
>, which
	  includes them. All Perl module installation steps require
	  you have an active Internet connection.  If you wish to use
	  Bundle::Bugzilla, however, you must be using the latest
	  version of Perl (at this writing, version 5.6.1)
	</P
><P
>&#13;	  <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash#</TT
> <B
CLASS="command"
>perl -MCPAN
	      -e 'install "Bundle::Bugzilla"'</B
>
	  </TT
>
	</P
><P
>&#13;	  Bundle::Bugzilla doesn't include GD, Chart::Base, or
	  MIME::Parser, which are not essential to a basic Bugzilla
	  install.  If installing this bundle fails, you should
	  install each module individually to isolate the problem.
	</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN602">3.2.5. DBI Perl Module</H2
><P
>&#13;	The DBI module is a generic Perl module used by other database related
	Perl modules.  For our purposes it's required by the MySQL-related
	modules.  As long as your Perl installation was done correctly the
	DBI module should be a breeze.  It's a mixed Perl/C module, but Perl's
	MakeMaker system simplifies the C compilation greatly.
      </P
><P
>&#13;	Like almost all Perl modules DBI can be found on the Comprehensive Perl
	Archive Network (CPAN) at http://www.cpan.org.  The CPAN servers have a
	real tendency to bog down, so please use mirrors.  The current location
	at the time of this writing can be found in <A
HREF="downloadlinks.html"
>Appendix B</A
>.
      </P
><P
>&#13;	Quality, general Perl module installation instructions can be found on
	the CPAN website, but the easy thing to do is to just use the CPAN shell
	which does all the hard work for you.
      </P
><P
>&#13;	To use the CPAN shell to install DBI:
	<DIV
CLASS="informalexample"
><A
NAME="AEN609"><P
></P
><P
>&#13;	    <TT
CLASS="computeroutput"
>&#13;	      <TT
CLASS="prompt"
>bash#</TT
>
	      <B
CLASS="command"
>perl -MCPAN -e 'install "DBI"'</B
>
	    </TT
>
	    <DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Replace "DBI" with the name of whichever module you wish
		to install, such as Data::Dumper, TimeDate, GD, etc.</P
></TD
></TR
></TABLE
></DIV
>
	  </P
><P
></P
></DIV
>
	To do it the hard way:
	<DIV
CLASS="informalexample"
><A
NAME="AEN616"><P
></P
><P
>&#13;	    Untar the module tarball -- it should create its own directory
	  </P
><P
>&#13;	    CD to the directory just created, and enter the following commands:
	    <P
></P
><OL
TYPE="1"
><LI
><P
>&#13;		  <TT
CLASS="computeroutput"
>&#13;		    <TT
CLASS="prompt"
>bash#</TT
>
		    <B
CLASS="command"
>perl Makefile.PL</B
>
		  </TT
>
		</P
></LI
><LI
><P
>&#13;		  <TT
CLASS="computeroutput"
>&#13;		    <TT
CLASS="prompt"
>bash#</TT
>
		    <B
CLASS="command"
>make</B
>
		  </TT
>
		</P
></LI
><LI
><P
>&#13;		  <TT
CLASS="computeroutput"
>&#13;		    <TT
CLASS="prompt"
>bash#</TT
>
		    <B
CLASS="command"
>make test</B
>
		  </TT
>
		</P
></LI
><LI
><P
>&#13;		  <TT
CLASS="computeroutput"
>&#13;		    <TT
CLASS="prompt"
>bash#</TT
>
		    <B
CLASS="command"
>make install</B
>
		  </TT
>
		</P
></LI
></OL
>
	    If everything went ok that should be all it takes.  For the vast
	    majority of perl modules this is all that's required.
	  </P
><P
></P
></DIV
>
      </P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN640">3.2.6. Data::Dumper Perl Module</H2
><P
>&#13;	The Data::Dumper module provides data structure persistence for Perl
	(similar to Java's serialization).  It comes with later sub-releases of
	Perl 5.004, but a re-installation just to be sure it's available won't
	hurt anything.
      </P
><P
>&#13;	Data::Dumper is used by the MySQL-related Perl modules.  It
	can be found on CPAN (see <A
HREF="downloadlinks.html"
>Appendix B</A
>) and
	can be
	installed by following the same four step make sequence used
	for the DBI module.
      </P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN645">3.2.7. MySQL related Perl Module Collection</H2
><P
>&#13;	The Perl/MySQL interface requires a few mutually-dependent perl
	modules.  These modules are grouped together into the the
	Msql-Mysql-modules package.  This package can be found at CPAN.
	After the archive file has been downloaded it should
	be untarred.
      </P
><P
>&#13;	The MySQL modules are all built using one make file which is generated
	by running:
	<TT
CLASS="prompt"
>bash#</TT
>
	<B
CLASS="command"
>perl Makefile.pl</B
>
      </P
><P
>&#13;	The MakeMaker process will ask you a few questions about the desired
	compilation target and your MySQL installation.  For many of the questions
	the provided default will be adequate.
      </P
><P
>&#13;	When asked if your desired target is the MySQL or mSQL packages,
	select the MySQL related ones.  Later you will be asked if you wish
	to provide backwards compatibility with the older MySQL packages; you
	  should answer YES to this question. The default is NO.
	</P
><P
>&#13;	  A host of 'localhost' should be fine and a testing user of 'test' and
	  a null password should find itself with sufficient access to run tests
	  on the 'test' database which MySQL created upon installation.  If 'make
	  test' and 'make install' go through without errors you should be ready
	  to go as far as database connectivity is concerned.
	</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN654">3.2.8. TimeDate Perl Module Collection</H2
><P
>&#13;	  Many of the more common date/time/calendar related Perl
	modules have been grouped into a bundle similar to the MySQL
	modules bundle. This bundle is stored on the CPAN under the
	name TimeDate (see link: <A
HREF="downloadlinks.html"
>Appendix B</A
>). The
	component module we're most interested in is the Date::Format
	module, but installing all of them is probably a good idea
	anyway.  The standard Perl module installation instructions
	should work perfectly for this simple package.
	</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN658">3.2.9. GD Perl Module (1.8.3)</H2
><P
>&#13;	  The GD library was written by Thomas Boutell a long while
	ago to programatically generate images in C.  Since then it's
	become the defacto standard for programatic image
	construction.  The Perl bindings to it found in the GD library
	are used on millions of web pages to generate graphs on the
	fly. That's what bugzilla will be using it for so you must
	install it if you want any of the graphing to work.
	</P
><P
>&#13;	  Actually bugzilla uses the Graph module which relies on GD
	itself.  Isn't that always the way with object-oriented
	programming?  At any rate, you can find the GD library on CPAN
	in <A
HREF="downloadlinks.html"
>Appendix B</A
>.  
	</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;	    The Perl GD library requires some other libraries that may
	  or may not be installed on your system, including
	  <TT
CLASS="classname"
>libpng</TT
> and
	  <TT
CLASS="classname"
>libgd</TT
>.  The full requirements are
	  listed in the Perl GD library README.  Just realize that if
	  compiling GD fails, it's probably because you're missing a
	  required library.
	  </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN667">3.2.10. Chart::Base Perl Module (0.99c)</H2
><P
>&#13;	  The Chart module provides bugzilla with on-the-fly charting
	abilities.  It can be installed in the usual fashion after it
	has been fetched from CPAN where it is found as the
	Chart-x.x... tarball, linked in <A
HREF="downloadlinks.html"
>Appendix B</A
>. Note that
	as with the GD perl module, only the version listed above, or
	newer, will work. Earlier versions used GIF's, which are no
	longer supported by the latest versions of GD.
	</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN671">3.2.11. DB_File Perl Module</H2
><P
>&#13;	  DB_File is a module which allows Perl programs to make use
	of the facilities provided by  Berkeley DB version 1.x. This
	module is required by collectstats.pl which is used for  bug
	charting. If you plan to make use of bug charting, you must
	install this module.
	</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN674">3.2.12. HTTP Server</H2
><P
>&#13;	  You have a freedom of choice here - Apache, Netscape or any
	other server on UNIX would do.  You can easily run the web
	server on a different machine than MySQL, but need to adjust
	the MySQL <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> user permissions accordingly.
	<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>I strongly recommend Apache as the web server to use.
	    The Bugzilla Guide installation instructions, in general,
	    assume you are using Apache.  As more users use different
	    webservers and send me information on the peculiarities of
	    installing using their favorite webserver, I will provide
	    notes for them.</P
></TD
></TR
></TABLE
></DIV
>
	</P
><P
>&#13;	  You'll want to make sure that your web server will run any
	file with the .cgi extension as a cgi and not just display it.
	If you're using apache that means uncommenting the following
	line in the srm.conf file:
	<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;AddHandler cgi-script .cgi
	</PRE
></FONT
></TD
></TR
></TABLE
>
	</P
><P
>&#13;	  With apache you'll also want to make sure that within the
	access.conf file the line:
 <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;Options ExecCGI
AllowOverride Limit
</PRE
></FONT
></TD
></TR
></TABLE
>
	is in the stanza that covers the directories into which
	you intend to put the bugzilla .html and .cgi files.
	</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          AllowOverride Limit allows the use of a Deny statement in the
          .htaccess file generated by checksetup.pl 
        </P
><P
>&#13;	  Users of newer versions of Apache will generally find both
	  of the above lines will be in the httpd.conf file, rather
	  than srm.conf or access.conf.
	</P
></TD
></TR
></TABLE
></DIV
><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
>&#13;	    There are important files and directories that should not
	  be a served by the HTTP server. These are most files in the
	  <SPAN
CLASS="QUOTE"
>"data"</SPAN
> and <SPAN
CLASS="QUOTE"
>"shadow"</SPAN
>  directories
	  and the <SPAN
CLASS="QUOTE"
>"localconfig"</SPAN
> file. You should
	  configure your HTTP server to not serve content from these
	  files. Failure to do so will expose critical passwords and
	  other data. Please see <A
HREF="geninstall.html#htaccess"
>.htaccess files and security</A
> for details
	  on how to do this for Apache.  I appreciate notes on how to
	  get this same functionality using other webservers.
	  </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN693">3.2.13. Installing the Bugzilla Files</H2
><P
>&#13;	  You should untar the Bugzilla files into a directory that
	you're willing to make writable by the default web server user
	(probably <SPAN
CLASS="QUOTE"
>"nobody"</SPAN
>).  You may decide to put the
	files off of the main web space for your web server or perhaps
	off of <TT
CLASS="filename"
>/usr/local</TT
> with a symbolic link in
	the web space that points to the Bugzilla directory.  At any
	rate, just dump all the files in the same place, and make sure
	you can access the files in that directory through your web
	server.
	</P
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;	    If you symlink the bugzilla directory into your Apache's
	  HTML heirarchy, you may receive
	  <SPAN
CLASS="errorname"
>Forbidden</SPAN
> errors unless you add the
	  <SPAN
CLASS="QUOTE"
>"FollowSymLinks"</SPAN
> directive to the
	  &#60;Directory&#62; entry for the HTML root.
	  </P
></TD
></TR
></TABLE
></DIV
><P
>&#13;	  Once all the files are in a web accessible directory, make
	that directory writable by your webserver's user.  This is a
	temporary step until you run the post-install
	<TT
CLASS="filename"
>checksetup.pl</TT
> script, which locks down your
	installation.
      </P
><P
>&#13;	Lastly, you'll need to set up a symbolic link to
	<TT
CLASS="filename"
>/usr/bonsaitools/bin/perl</TT
> for the correct
	location of your perl executable (probably
	<TT
CLASS="filename"
>/usr/bin/perl</TT
>). Otherwise you must hack
	all the .cgi files to change where they look for perl, or use
	<A
HREF="setperl.html"
>The setperl.csh Utility</A
>, found in
	<A
HREF="patches.html"
>Useful Patches and Utilities for Bugzilla</A
>.  I suggest using the symlink
	approach for future release compatability.
	<DIV
CLASS="example"
><A
NAME="AEN709"><P
><B
>Example 3-1. Setting up bonsaitools symlink</B
></P
><P
>&#13;	      Here's how you set up the Perl symlink on Linux to make
	    Bugzilla work. Your mileage may vary.  For some UNIX
	    operating systems, you probably need to subsitute
	    <SPAN
CLASS="QUOTE"
>"/usr/local/bin/perl"</SPAN
> for
	    <SPAN
CLASS="QUOTE"
>"/usr/bin/perl"</SPAN
>  below; if on certain other
	    UNIX systems, Perl may live in weird places like
	    <SPAN
CLASS="QUOTE"
>"/opt/perl"</SPAN
>.  As root, run these commands:
	    <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;bash# mkdir /usr/bonsaitools  
bash# mkdir /usr/bonsaitools/bin 
bash# ln -s /usr/bin/perl /usr/bonsaitools/bin/perl
	    </PRE
></FONT
></TD
></TR
></TABLE
>
	  </P
><P
>&#13;	    Alternately, you can simply run this perl one-liner to
	    change your path to perl in all the files in your Bugzilla
	    installation:
	    <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm processmail syncshadowdb
	    </PRE
></FONT
></TD
></TR
></TABLE
>
	    Change the second path to perl to match your installation.
	  </P
></DIV
>
	<DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;	    If you don't have root access to set this symlink up,
	    check out the
	    <A
HREF="setperl.html"
>The setperl.csh Utility</A
>, listed in <A
HREF="patches.html"
>Useful Patches and Utilities for Bugzilla</A
>. It will change the path to perl in all your Bugzilla files for you.
	  </P
></TD
></TR
></TABLE
></DIV
>
	</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN722">3.2.14. Setting Up the MySQL Database</H2
><P
>&#13;	  After you've gotten all the software installed and working you're ready
	  to start preparing the database for its life as a the back end to a high
	  quality bug tracker.
	</P
><P
>&#13;	  First, you'll want to fix MySQL permissions to allow access
	from Bugzilla.  For the purpose of this Installation section,
	the Bugzilla username will be <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
>, and will
	have minimal permissions.
	
	<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
>&#13;	    Bugzilla has not undergone a thorough security audit. It
	    may be possible for a system cracker to somehow trick
	    Bugzilla into executing a command such as <B
CLASS="command"
>DROP
	      DATABASE mysql</B
>.
	  </P
><P
>That would be bad.</P
></TD
></TR
></TABLE
></DIV
>
      </P
><P
>&#13;	Give the MySQL root user a password.  MySQL passwords are
	limited to 16 characters.
	<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash#</TT
> <B
CLASS="command"
>mysql
		-u root mysql</B
> </TT
>
	  </TD
></TR
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>mysql&#62;</TT
> <B
CLASS="command"
>&#13;		UPDATE user SET Password=PASSWORD ('new_password')
		WHERE user='root'; </B
> </TT
>
	  </TD
></TR
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>mysql&#62;</TT
> <B
CLASS="command"
>FLUSH
		PRIVILEGES;</B
> </TT
>
	  </TD
></TR
></TBODY
></TABLE
><P
></P
> From this point on, if you need to access
	MySQL as the MySQL root user, you will need to use
	<B
CLASS="command"
>mysql -u root -p</B
> and enter your
	new_password.  Remember that MySQL user names have nothing to
	do with Unix user names (login names).	  
      </P
><P
>&#13;	Next, we create the <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> user, and grant
	sufficient permissions for checksetup.pl, which we'll use
	later, to work its magic.  This also restricts the
	<SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> user to operations within a database
	called <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
>, and only allows the account to
	connect from <SPAN
CLASS="QUOTE"
>"localhost"</SPAN
>.  Modify it to reflect
	your setup if you will be connecting from another machine or
	as a different user.
      </P
><P
>&#13;	Remember to set bugs_password to some unique password.
	<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
>&#13;	      <TT
CLASS="prompt"
>mysql&#62;</TT
>
	      <B
CLASS="command"
>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,
		ALTER,CREATE,DROP,REFERENCES 
		ON bugs.* TO bugs@localhost
		IDENTIFIED BY 'bugs_password';</B
>
	    </TT
>
	  </TD
></TR
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
>&#13;	      <TT
CLASS="prompt"
>&#13;		mysql&#62;
	      </TT
>
	      <B
CLASS="command"
>&#13;		FLUSH PRIVILEGES;
	      </B
>
	    </TT
>
	  </TD
></TR
></TBODY
></TABLE
><P
></P
>
      </P
><P
>&#13;	Next, run the magic checksetup.pl script.  (Many thanks to
	Holger Schurig &#60;holgerschurig@nikocity.de&#62; for writing
	this script!) It will make sure Bugzilla files and directories
	have reasonable permissions, set up the
	<TT
CLASS="filename"
>data</TT
> directory, and create all the MySQL
	tables.
	<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash#</TT
>
	      <B
CLASS="command"
>./checksetup.pl</B
> </TT
>
	  </TD
></TR
></TBODY
></TABLE
><P
></P
> The first time you run it, it will create a
	file called <TT
CLASS="filename"
>localconfig</TT
>.
      </P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN769">3.2.15. Tweaking <TT
CLASS="filename"
>localconfig</TT
></H2
><P
>&#13;	This file contains a variety of settings you may need to tweak including
	how Bugzilla should connect to the MySQL database.
      </P
><P
>&#13;	The connection settings include:
	<P
></P
><OL
TYPE="1"
><LI
><P
>&#13;	      server's host: just use <SPAN
CLASS="QUOTE"
>"localhost"</SPAN
> if the
	      MySQL server is local
	    </P
></LI
><LI
><P
>&#13;	      database name: <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> if you're following
	      these directions
	    </P
></LI
><LI
><P
>&#13;	      MySQL username: <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> if you're following
	      these directions
	    </P
></LI
><LI
><P
>&#13;	      Password for the <SPAN
CLASS="QUOTE"
>"bugs"</SPAN
> MySQL account above
	    </P
></LI
></OL
>
      </P
><P
>&#13;	You should also install .htaccess files that the Apache
	webserver will use  to restrict access to Bugzilla data files.
	See <A
HREF="geninstall.html#htaccess"
>.htaccess files and security</A
>.
      </P
><P
>&#13;	Once you are happy with the settings, re-run
	<TT
CLASS="filename"
>checksetup.pl</TT
>. On this second run, it will
	  create the database and an administrator account for which
	  you will be prompted to provide information.
      </P
><P
>&#13;	When logged into an administrator account once Bugzilla is
	running, if you go to the query page (off of the Bugzilla main
	menu), you'll find an <SPAN
CLASS="QUOTE"
>"edit parameters"</SPAN
> option
	that is filled with editable treats.
      </P
><P
>&#13;	Should everything work, you will have a nearly empty Bugzilla
	database and a newly-created <TT
CLASS="filename"
>localconfig</TT
>
	file in your Bugzilla root directory.
      </P
><P
>&#13;	<DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;	    The second time you run checksetup.pl, you should become
	    the user your web server runs as, and that you ensure that
	    you set the <SPAN
CLASS="QUOTE"
>"webservergroup"</SPAN
> parameter in localconfig to
	    match the web  server's group name, if any.  I believe,
	    for the next release of Bugzilla, this will be fixed so
	    that Bugzilla supports a <SPAN
CLASS="QUOTE"
>"webserveruser"</SPAN
> parameter in
	    localconfig as well.
	    <DIV
CLASS="example"
><A
NAME="AEN800"><P
><B
>Example 3-2. Running checksetup.pl as the web user</B
></P
><P
>&#13;		  Assuming your web server runs as user "apache", and
		Bugzilla is installed in "/usr/local/bugzilla", here's
		one way to run checksetup.pl as the web server user.
		As root, for the <EM
>second run</EM
> of
		checksetup.pl, do this: 
		<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
> 
bash# chown -R apache:apache /usr/local/bugzilla 
bash# su - apache 
bash# cd /usr/local/bugzilla 
bash# ./checksetup.pl 
		</PRE
></FONT
></TD
></TR
></TABLE
>
	      </P
></DIV
>
	  </P
></TD
></TR
></TABLE
></DIV
>
      </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;	  The checksetup.pl script is designed so that you can run
	  it at any time without causing harm.  You should run it
	  after any upgrade to Bugzilla.
	</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN807">3.2.16. Setting Up Maintainers Manually (Optional)</H2
><P
>&#13;	If you want to add someone else to every group by hand, you
	can do it by typing the appropriate MySQL commands.  Run
	<B
CLASS="command"
> mysql -u root -p bugs</B
> You
	may need different parameters, depending on your security
	settings. Then:
	  <P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;	      <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>mysql&#62;</TT
> <B
CLASS="command"
>update
		profiles set groupset=0x7fffffffffffffff where
		login_name = 'XXX';</B
> </TT
> (yes, that's <EM
>fifteen</EM
><SPAN
CLASS="QUOTE"
>"f"</SPAN
>'s.
	    </TD
></TR
></TBODY
></TABLE
><P
></P
> replacing XXX with the Bugzilla email address.
	</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN818">3.2.17. The Whining Cron (Optional)</H2
><P
>&#13;	By now you have a fully functional bugzilla, but what good
	are bugs if they're not annoying?  To help make those bugs
	more annoying you can set up bugzilla's automatic whining
	system.  This can be done by adding the following command as a
	daily crontab entry (for help on that see that crontab man
	page):
	<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
> <B
CLASS="command"
>cd
		&#60;your-bugzilla-directory&#62; ;
		./whineatnews.pl</B
> </TT
>
	  </TD
></TR
></TBODY
></TABLE
><P
></P
>
      </P
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;	  Depending on your system, crontab may have several manpages.
	  The following command should  lead you to the most useful
	  page for this purpose: 
	  <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13; man 5 crontab
	  </PRE
></FONT
></TD
></TR
></TABLE
>
	</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN828">3.2.18. Bug Graphs (Optional)</H2
><P
>&#13;	As long as you installed the GD and Graph::Base Perl modules
	you might as well turn on the nifty bugzilla bug reporting
	graphs.
      </P
><P
>&#13;	Add a cron entry like this to run collectstats daily at 5
	after midnight:
	<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
> <TT
CLASS="prompt"
>bash#</TT
> <B
CLASS="command"
>crontab
		-e</B
> </TT
>
	  </TD
></TR
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
> 5 0 * * * cd
	      &#60;your-bugzilla-directory&#62; ; ./collectstats.pl
	    </TT
>
	  </TD
></TR
></TBODY
></TABLE
><P
></P
>
      </P
><P
>&#13;	After two days have passed you'll be able to view bug graphs
	from the Bug Reports page. 
      </P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN840">3.2.19. Securing MySQL</H2
><P
>&#13;	If you followed the installation instructions for setting up
	your "bugs" and "root" user in MySQL, much of this should not
	apply to you.  If you are upgrading an existing installation
	of Bugzilla, you should pay close attention to this section.
      </P
><P
>&#13;	Most MySQL installs have "interesting" default security parameters:
	<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>mysqld defaults to running as root</TD
></TR
><TR
><TD
>it defaults to allowing external network connections</TD
></TR
><TR
><TD
>it has a known port number, and is easy to detect</TD
></TR
><TR
><TD
>it defaults to no passwords whatsoever</TD
></TR
><TR
><TD
>it defaults to allowing "File_Priv"</TD
></TR
></TBODY
></TABLE
><P
></P
>
      </P
><P
>&#13;	This means anyone from anywhere on the internet can not only
	drop the database with one SQL command, and they can write as
	root to the system.
      </P
><P
>&#13;	To see your permissions do:
	<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
>&#13;	      <TT
CLASS="prompt"
>bash#</TT
>
	      <B
CLASS="command"
>mysql -u root -p</B
>
	    </TT
>
	  </TD
></TR
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
>&#13;	      <TT
CLASS="prompt"
>mysql&#62;</TT
>
	      <B
CLASS="command"
>use mysql;</B
>
	    </TT
>
	  </TD
></TR
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
>&#13;	      <TT
CLASS="prompt"
>mysql&#62;</TT
>
	      <B
CLASS="command"
>show tables;</B
>
	    </TT
>
	  </TD
></TR
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
>&#13;	      <TT
CLASS="prompt"
>mysql&#62;</TT
>
	      <B
CLASS="command"
>select * from user;</B
>
	    </TT
>
	  </TD
></TR
><TR
><TD
>&#13;	    <TT
CLASS="computeroutput"
>&#13;	      <TT
CLASS="prompt"
>mysql&#62;</TT
>
	      <B
CLASS="command"
>select * from db;</B
>
	    </TT
>
	  </TD
></TR
></TBODY
></TABLE
><P
></P
>
      </P
><P
>&#13;	To fix the gaping holes:
	<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>DELETE FROM user WHERE User='';</TD
></TR
><TR
><TD
>UPDATE user SET Password=PASSWORD('new_password') WHERE user='root';</TD
></TR
><TR
><TD
> FLUSH PRIVILEGES;</TD
></TR
></TBODY
></TABLE
><P
></P
>
      </P
><P
>&#13;	If you're not running "mit-pthreads" you can use:
	<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>GRANT USAGE ON *.* TO bugs@localhost;</TD
></TR
><TR
><TD
>GRANT ALL ON bugs.* TO bugs@localhost;</TD
></TR
><TR
><TD
>REVOKE DROP ON bugs.* FROM bugs@localhost;</TD
></TR
><TR
><TD
>FLUSH PRIVILEGES;</TD
></TR
></TBODY
></TABLE
><P
></P
>
      </P
><P
>&#13;	With "mit-pthreads" you'll need to modify the "globals.pl" Mysql-&#62;Connect
	line to specify a specific host name instead of "localhost", and accept
	external connections:
	<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>GRANT USAGE ON *.* TO bugs@bounce.hop.com;</TD
></TR
><TR
><TD
>GRANT ALL ON bugs.* TO bugs@bounce.hop.com;</TD
></TR
><TR
><TD
>REVOKE DROP ON bugs.* FROM bugs@bounce.hop.com;</TD
></TR
><TR
><TD
>FLUSH PRIVILEGES;</TD
></TR
></TBODY
></TABLE
><P
></P
>
      </P
><P
>&#13;	Use .htaccess files with the Apache webserver to secure your
	bugzilla install. See <A
HREF="geninstall.html#htaccess"
>.htaccess files and security</A
>
      </P
><P
>&#13;	Consider also:
	<P
></P
><OL
TYPE="1"
><LI
><P
>&#13;	      Turning off external networking with "--skip-networking",
	      unless you have "mit-pthreads", in which case you can't.
	      Without networking, MySQL connects with a Unix domain socket.
	    </P
></LI
><LI
><P
>&#13;	      using the --user= option to mysqld to run it as an unprivileged
	      user.
	    </P
></LI
><LI
><P
>&#13;	      starting MySQL in a chroot jail
	    </P
></LI
><LI
><P
>&#13;	      running the httpd in a "chrooted" jail
	    </P
></LI
><LI
><P
>&#13;	      making sure the MySQL passwords are different from the OS
	      passwords (MySQL "root" has nothing to do with system "root").
	    </P
></LI
><LI
><P
>&#13;	      running MySQL on a separate untrusted machine
	    </P
></LI
><LI
><P
>&#13;	      making backups ;-)
	    </P
></LI
></OL
>
      </P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="errata.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="osx.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>ERRATA</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="installation.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Mac OS X Installation Notes</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>