~ubuntu-branches/ubuntu/gutsy/bugzilla/gutsy-security : revision 3

1

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

1

2

<HTML

2

3

><HEAD

3

4

><TITLE

4

>The Bugzilla Guide - 2.16.4 Release</TITLE

5

>The Bugzilla Guide - 2.16.7 Release</TITLE

5

6

><META

6

7

NAME="GENERATOR"

7

8

CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><META

41

42

CLASS="title"

42

43

><A

43

44

NAME="AEN2"

44

></A

45

>The Bugzilla Guide - 2.16.4 Release</H1

45

>The Bugzilla Guide - 2.16.7 Release</A

46

></H1

46

47

><H3

47

48

CLASS="author"

48

49

><A

57

58

>The Bugzilla Team</H3

58

59

><P

59

60

CLASS="pubdate"

60

>2003-11-01<BR></P

61

>2004-07-10<BR></P

61

62

><DIV

62

63

><DIV

63

64

CLASS="abstract"

65

><P

66

></P

64

67

><A

65

68

NAME="AEN14"

66

69

></A

67

70

><P

68

></P

69

><P

70

71

> This is the documentation for Bugzilla, the mozilla.org

71

72

bug-tracking system.

72

73

Bugzilla is an enterprise-class piece of software

79

80

Changes are best submitted as plain text or XML diffs, attached

80

81

to a bug filed in

81

82

<A

82

HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"

83

HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"

83

84

TARGET="_top"

84

85

>mozilla.org's Bugzilla</A

85

86

>.

210

211

></DT

211

212

><DT

212

213

>4.5. <A

214

HREF="#nonroot"

215

>UNIX (non-root) Installation Notes</A

216

></DT

217

><DT

218

>4.6. <A

213

219

HREF="#troubleshooting"

214

220

>Troubleshooting</A

215

221

></DT

463

469

></DT

464

470

><DT

465

471

>4-1. <A

466

HREF="#AEN863"

472

HREF="#AEN878"

467

473

>Installing ActivePerl ppd Modules on Microsoft

468

474

Windows</A

469

475

></DT

470

476

><DT

471

477

>4-2. <A

472

HREF="#AEN876"

478

HREF="#AEN892"

473

479

>Installing OpenInteract ppd Modules manually on Microsoft

474

480

Windows</A

475

481

></DT

476

482

><DT

477

483

>4-3. <A

478

HREF="#AEN1058"

484

HREF="#AEN1074"

479

485

>Removing encrypt() for Windows NT Bugzilla version 2.12 or

480

486

earlier</A

481

487

></DT

505

511

>Chapter 1. About This Guide</H1

506

512

><DIV

507

513

CLASS="section"

508

><H1

514

><H2

509

515

CLASS="section"

510

516

><A

511

517

NAME="copyright"

512

></A

513

>1.1. Copyright Information</H1

518

>1.1. Copyright Information</A

519

></H2

514

520

><A

515

521

NAME="AEN34"

516

522

></A

526

532

VALIGN="TOP"

527

533

> </TD

528

534

><TD

529

WIDTH="80%"

530

535

VALIGN="TOP"

531

536

><P

532

537

> Permission is granted to copy, distribute and/or modify this

567

572

></DIV

568

573

><DIV

569

574

CLASS="section"

570

><HR><H1

575

><HR><H2

571

576

CLASS="section"

572

577

><A

573

578

NAME="disclaimer"

574

></A

575

>1.2. Disclaimer</H1

579

>1.2. Disclaimer</A

580

></H2

576

581

><P

577

582

> No liability for the contents of this document can be accepted.

578

583

Use the concepts, examples, and other content at your own risk.

617

622

></DIV

618

623

><DIV

619

624

CLASS="section"

620

><HR><H1

625

><HR><H2

621

626

CLASS="section"

622

627

><A

623

628

NAME="newversions"

624

></A

625

>1.3. New Versions</H1

629

>1.3. New Versions</A

630

></H2

626

631

><P

627

> This is the 2.16.4 version of The Bugzilla Guide. It is so named

632

> This is the 2.16.7 version of The Bugzilla Guide. It is so named

628

633

to match the version of Bugzilla it is disributed with. If you are

629

634

reading this from any source other than those below, please

630

635

check one of these mirrors to make sure you are reading an

673

678

></DIV

674

679

><DIV

675

680

CLASS="section"

676

><HR><H1

681

><HR><H2

677

682

CLASS="section"

678

683

><A

679

684

NAME="credits"

680

></A

681

>1.4. Credits</H1

685

>1.4. Credits</A

686

></H2

682

687

><P

683

688

> The people listed below have made enormous contributions to the

684

689

creation of this Guide, through their writing, dedicated hacking efforts,

691

696

CLASS="variablelist"

692

697

><DL

693

698

><DT

694

>Matthew P. Barnson <TT

699

>Matthew P. Barnson <CODE

695

700

CLASS="email"

696

701

><<A

697

702

HREF="mailto:mbarnson@sisna.com"

698

703

>mbarnson@sisna.com</A

699

>></TT

704

>></CODE

700

705

></DT

701

706

><DD

702

707

><P

705

710

</P

706

711

></DD

707

712

><DT

708

>Terry Weissman <TT

713

>Terry Weissman <CODE

709

714

CLASS="email"

710

715

><<A

711

716

HREF="mailto:terry@mozilla.org"

712

717

>terry@mozilla.org</A

713

>></TT

718

>></CODE

714

719

></DT

715

720

><DD

716

721

><P

719

724

</P

720

725

></DD

721

726

><DT

722

>Tara Hernandez <TT

727

>Tara Hernandez <CODE

723

728

CLASS="email"

724

729

><<A

725

730

HREF="mailto:tara@tequilarists.org"

726

731

>tara@tequilarists.org</A

727

>></TT

732

>></CODE

728

733

></DT

729

734

><DD

730

735

><P

733

738

</P

734

739

></DD

735

740

><DT

736

>Dave Lawrence <TT

741

>Dave Lawrence <CODE

737

742

CLASS="email"

738

743

><<A

739

744

HREF="mailto:dkl@redhat.com"

740

745

>dkl@redhat.com</A

741

>></TT

746

>></CODE

742

747

></DT

743

748

><DD

744

749

><P

751

756

</P

752

757

></DD

753

758

><DT

754

>Dawn Endico <TT

759

>Dawn Endico <CODE

755

760

CLASS="email"

756

761

><<A

757

762

HREF="mailto:endico@mozilla.org"

758

763

>endico@mozilla.org</A

759

>></TT

764

>></CODE

760

765

></DT

761

766

><DD

762

767

><P

765

770

</P

766

771

></DD

767

772

><DT

768

>Jacob Steenhagen <TT

773

>Jacob Steenhagen <CODE

769

774

CLASS="email"

770

775

><<A

771

776

HREF="mailto:jake@bugzilla.org"

772

777

>jake@bugzilla.org</A

773

>></TT

778

>></CODE

774

779

></DT

775

780

><DD

776

781

><P

799

804

></DIV

800

805

><DIV

801

806

CLASS="section"

802

><HR><H1

807

><HR><H2

803

808

CLASS="section"

804

809

><A

805

810

NAME="conventions"

806

></A

807

>1.5. Document Conventions</H1

811

>1.5. Document Conventions</A

812

></H2

808

813

><P

809

814

>This document uses the following conventions:</P

810

815

><DIV

811

816

CLASS="informaltable"

817

><P

818

></P

812

819

><A

813

820

NAME="AEN111"

814

821

></A

815

><P

816

></P

817

822

><TABLE

818

823

BORDER="0"

824

FRAME="void"

819

825

CLASS="CALSTABLE"

820

><THEAD

826

><COL><COL><THEAD

821

827

><TR

822

828

><TH

823

ALIGN="LEFT"

824

VALIGN="MIDDLE"

825

829

>Descriptions</TH

826

830

><TH

827

ALIGN="LEFT"

828

VALIGN="MIDDLE"

829

831

>Appearance</TH

830

832

></TR

831

833

></THEAD

832

834

><TBODY

833

835

><TR

834

836

><TD

835

ALIGN="LEFT"

836

VALIGN="MIDDLE"

837

>Use caution</TD

838

><TD

839

ALIGN="LEFT"

840

VALIGN="MIDDLE"

841

839

> <DIV

842

840

CLASS="caution"

843

841

><P

869

867

></TR

870

868

><TR

871

869

><TD

872

ALIGN="LEFT"

873

VALIGN="MIDDLE"

874

870

>Hint</TD

875

871

><TD

876

ALIGN="LEFT"

877

VALIGN="MIDDLE"

878

872

> <DIV

879

873

CLASS="tip"

880

874

><P

906

900

></TR

907

901

><TR

908

902

><TD

909

ALIGN="LEFT"

910

VALIGN="MIDDLE"

911

903

>Notes</TD

912

904

><TD

913

ALIGN="LEFT"

914

VALIGN="MIDDLE"

915

905

> <DIV

916

906

CLASS="note"

917

907

><P

943

933

></TR

944

934

><TR

945

935

><TD

946

ALIGN="LEFT"

947

VALIGN="MIDDLE"

948

936

>Warnings</TD

949

937

><TD

950

ALIGN="LEFT"

951

VALIGN="MIDDLE"

952

938

> <DIV

953

939

CLASS="warning"

954

940

><P

980

966

></TR

981

967

><TR

982

968

><TD

983

ALIGN="LEFT"

984

VALIGN="MIDDLE"

985

969

>File Names</TD

986

970

><TD

987

ALIGN="LEFT"

988

VALIGN="MIDDLE"

989

971

> <TT

990

972

CLASS="filename"

991

973

>filename</TT

994

976

></TR

995

977

><TR

996

978

><TD

997

ALIGN="LEFT"

998

VALIGN="MIDDLE"

999

979

>Directory Names</TD

1000

980

><TD

1001

ALIGN="LEFT"

1002

VALIGN="MIDDLE"

1003

981

> <TT

1004

982

CLASS="filename"

1005

983

>directory</TT

1008

986

></TR

1009

987

><TR

1010

988

><TD

1011

ALIGN="LEFT"

1012

VALIGN="MIDDLE"

1013

989

>Commands to be typed</TD

1014

990

><TD

1015

ALIGN="LEFT"

1016

VALIGN="MIDDLE"

1017

991

> <B

1018

992

CLASS="command"

1019

993

>command</B

1022

996

></TR

1023

997

><TR

1024

998

><TD

1025

ALIGN="LEFT"

1026

VALIGN="MIDDLE"

1027

999

>Applications Names</TD

1028

1000

><TD

1029

ALIGN="LEFT"

1030

VALIGN="MIDDLE"

1031

1001

> <SPAN

1032

1002

CLASS="application"

1033

1003

>application</SPAN

1036

1006

></TR

1037

1007

><TR

1038

1008

><TD

1039

ALIGN="LEFT"

1040

VALIGN="MIDDLE"

1041

1009

> <I

1042

1010

CLASS="foreignphrase"

1043

1011

>Prompt</I

1045

1013

1046

1014

of users command under bash shell</TD

1047

1015

><TD

1048

ALIGN="LEFT"

1049

VALIGN="MIDDLE"

1050

1016

>bash$</TD

1051

1017

></TR

1052

1018

><TR

1053

1019

><TD

1054

ALIGN="LEFT"

1055

VALIGN="MIDDLE"

1056

1020

> <I

1057

1021

CLASS="foreignphrase"

1058

1022

>Prompt</I

1060

1024

1061

1025

of root users command under bash shell</TD

1062

1026

><TD

1063

ALIGN="LEFT"

1064

VALIGN="MIDDLE"

1065

1027

>bash#</TD

1066

1028

></TR

1067

1029

><TR

1068

1030

><TD

1069

ALIGN="LEFT"

1070

VALIGN="MIDDLE"

1071

1031

> <I

1072

1032

CLASS="foreignphrase"

1073

1033

>Prompt</I

1075

1035

1076

1036

of user command under tcsh shell</TD

1077

1037

><TD

1078

ALIGN="LEFT"

1079

VALIGN="MIDDLE"

1080

1038

>tcsh$</TD

1081

1039

></TR

1082

1040

><TR

1083

1041

><TD

1084

ALIGN="LEFT"

1085

VALIGN="MIDDLE"

1086

1042

>Environment Variables</TD

1087

1043

><TD

1088

ALIGN="LEFT"

1089

VALIGN="MIDDLE"

1090

> <TT

1044

> <VAR

1091

1045

CLASS="envar"

1092

>VARIABLE</TT

1046

>VARIABLE</VAR

1093

1047

>

1094

1048

</TD

1095

1049

></TR

1096

1050

><TR

1097

1051

><TD

1098

ALIGN="LEFT"

1099

VALIGN="MIDDLE"

1100

1052

>Emphasized word</TD

1101

1053

><TD

1102

ALIGN="LEFT"

1103

VALIGN="MIDDLE"

1104

1054

> <EM

1105

1055

>word</EM

1106

1056

>

1108

1058

></TR

1109

1059

><TR

1110

1060

><TD

1111

ALIGN="LEFT"

1112

VALIGN="MIDDLE"

1113

1061

>Term found in the glossary</TD

1114

1062

><TD

1115

ALIGN="LEFT"

1116

VALIGN="MIDDLE"

1117

1063

> <A

1118

1064

HREF="#gloss-bugzilla"

1119

1065

><I

1125

1071

></TR

1126

1072

><TR

1127

1073

><TD

1128

ALIGN="LEFT"

1129

VALIGN="MIDDLE"

1130

1074

>Code Example</TD

1131

1075

><TD

1132

ALIGN="LEFT"

1133

VALIGN="MIDDLE"

1134

1076

> <TABLE

1135

1077

BORDER="0"

1136

1078

BGCOLOR="#E0E0E0"

1141

1083

COLOR="#000000"

1142

1084

><PRE

1143

1085

CLASS="programlisting"

1144

><TT

1086

><CODE

1145

1087

CLASS="sgmltag"

1146

><para></TT

1088

><para></CODE

1147

1089

>

1148

1090

Beginning and end of paragraph

1149

<TT

1091

<CODE

1150

1092

CLASS="sgmltag"

1151

></para></TT

1093

></para></CODE

1152

1094

></PRE

1153

1095

></FONT

1154

1096

></TD

1173

1115

>Chapter 2. Introduction</H1

1174

1116

><DIV

1175

1117

CLASS="section"

1176

><H1

1118

><H2

1177

1119

CLASS="section"

1178

1120

><A

1179

1121

NAME="whatis"

1180

></A

1181

>2.1. What is Bugzilla?</H1

1122

>2.1. What is Bugzilla?</A

1123

></H2

1182

1124

><P

1183

1125

> Bugzilla is a bug- or issue-tracking system. Bug-tracking

1184

1126

systems allow individual or groups of developers effectively to keep track

1259

1201

></DIV

1260

1202

><DIV

1261

1203

CLASS="section"

1262

><HR><H1

1204

><HR><H2

1263

1205

CLASS="section"

1264

1206

><A

1265

1207

NAME="why"

1266

></A

1267

>2.2. Why Should We Use Bugzilla?</H1

1208

>2.2. Why Should We Use Bugzilla?</A

1209

></H2

1268

1210

><P

1269

1211

>For many years, defect-tracking software has remained principally

1270

1212

the domain of large software development houses. Even then, most shops

1341

1283

>Chapter 3. Using Bugzilla</H1

1342

1284

><DIV

1343

1285

CLASS="section"

1344

><H1

1286

><H2

1345

1287

CLASS="section"

1346

1288

><A

1347

1289

NAME="how"

1348

></A

1349

>3.1. How do I use Bugzilla?</H1

1290

>3.1. How do I use Bugzilla?</A

1291

></H2

1350

1292

><P

1351

>This section contains information for end-users of Bugzilla.

1352

There is a Bugzilla test installation, called

1293

>This section contains information for end-users of Bugzilla. There

1294

is a Bugzilla test installation, called

1353

1295

<A

1354

1296

HREF="http://landfill.bugzilla.org/"

1355

1297

TARGET="_top"

1356

1298

>Landfill</A

1357

>,

1358

which you are welcome to play with (if it's up.)

1359

However, it does not necessarily

1360

have all Bugzilla features enabled, and often runs cutting-edge versions

1361

of Bugzilla for testing, so some things may work slightly differently

1362

than mentioned here.</P

1299

>, which you are

1300

welcome to play with (if it's up). However, not all of the Bugzilla

1301

installations there will necessarily have all Bugzilla features enabled,

1302

and different installations run different versions, so some things may not

1303

quite work as this document describes.</P

1363

1304

><DIV

1364

1305

CLASS="section"

1365

><HR><H2

1306

><HR><H3

1366

1307

CLASS="section"

1367

1308

><A

1368

1309

NAME="myaccount"

1369

></A

1370

>3.1.1. Create a Bugzilla Account</H2

1310

>3.1.1. Create a Bugzilla Account</A

1311

></H3

1371

1312

><P

1372

1313

>If you want to use Bugzilla, first you need to create an account.

1373

1314

Consult with the administrator responsible for your installation of

1374

1315

Bugzilla for the URL you should use to access it. If you're

1375

1316

test-driving Bugzilla, use this URL:

1376

1317

<A

1377

HREF="http://landfill.bugzilla.org/bugzilla-tip/"

1318

HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/"

1378

1319

TARGET="_top"

1379

> http://landfill.bugzilla.org/bugzilla-tip/</A

1320

>http://landfill.bugzilla.org/bugzilla-2.16.7/</A

1380

1321

>

1381

1322

</P

1382

1323

><P

1432

1373

></DIV

1433

1374

><DIV

1434

1375

CLASS="section"

1435

><HR><H2

1376

><HR><H3

1436

1377

CLASS="section"

1437

1378

><A

1438

1379

NAME="bug_page"

1439

></A

1440

>3.1.2. Anatomy of a Bug</H2

1380

>3.1.2. Anatomy of a Bug</A

1381

></H3

1441

1382

><P

1442

1383

>The core of Bugzilla is the screen which displays a particular

1443

1384

bug. It's a good place to explain some Bugzilla concepts.

1444

1385

<A

1445

HREF="http://landfill.bugzilla.org/bugzilla-tip/show_bug.cgi?id=1"

1386

HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/show_bug.cgi?id=1"

1446

1387

TARGET="_top"

1447

1388

> Bug 1 on Landfill</A

1448

1389

>

1699

1640

></DIV

1700

1641

><DIV

1701

1642

CLASS="section"

1702

><HR><H2

1643

><HR><H3

1703

1644

CLASS="section"

1704

1645

><A

1705

1646

NAME="query"

1706

></A

1707

>3.1.3. Searching for Bugs</H2

1647

>3.1.3. Searching for Bugs</A

1648

></H3

1708

1649

><P

1709

1650

>The Bugzilla Search page is is the interface where you can find

1710

1651

any bug report, comment, or patch currently in the Bugzilla system. You

1711

1652

can play with it here:

1712

1653

<A

1713

HREF="http://landfill.bugzilla.org/bugzilla-tip/query.cgi"

1654

HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/query.cgi"

1714

1655

TARGET="_top"

1715

> landfill.bugzilla.org/bugzilla-tip/query.cgi</A

1656

>http://landfill.bugzilla.org/bugzilla-2.16.7/query.cgi</A

1716

1657

>

1717

1658

1718

1659

.</P

1725

1666

>Highly advanced querying is done using Boolean Charts, which have

1726

1667

their own

1727

1668

<A

1728

HREF="http://landfill.bugzilla.org/bugzilla-tip/booleanchart.html"

1669

HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/booleanchart.html"

1729

1670

TARGET="_top"

1730

1671

> context-sensitive help</A

1731

1672

>

1734

1675

></DIV

1735

1676

><DIV

1736

1677

CLASS="section"

1737

><HR><H2

1678

><HR><H3

1738

1679

CLASS="section"

1739

1680

><A

1740

1681

NAME="list"

1741

></A

1742

>3.1.4. Bug Lists</H2

1682

>3.1.4. Bug Lists</A

1683

></H3

1743

1684

><P

1744

1685

>If you run a search, a list of matching bugs will be returned.

1745

1686

The default search is to return all open bugs on the system - don't try

1808

1749

></DIV

1809

1750

><DIV

1810

1751

CLASS="section"

1811

><HR><H2

1752

><HR><H3

1812

1753

CLASS="section"

1813

1754

><A

1814

1755

NAME="bugreports"

1815

></A

1816

>3.1.5. Filing Bugs</H2

1756

>3.1.5. Filing Bugs</A

1757

></H3

1817

1758

><P

1818

1759

>Years of bug writing experience has been distilled for your

1819

1760

reading pleasure into the

1820

1761

<A

1821

HREF="http://landfill.bugzilla.org/bugzilla-tip/bugwritinghelp.html"

1762

HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/bugwritinghelp.html"

1822

1763

TARGET="_top"

1823

1764

> Bug Writing Guidelines</A

1824

1765

>.

1838

1779

><P

1839

1780

>Go to

1840

1781

<A

1841

HREF="http://landfill.bugzilla.org/bugzilla-tip/"

1782

HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/"

1842

1783

TARGET="_top"

1843

1784

> Landfill</A

1844

1785

>

1845

1786

in your browser and click

1846

1787

<A

1847

HREF="http://landfill.bugzilla.org/bugzilla-tip/enter_bug.cgi"

1788

HREF="http://landfill.bugzilla.org/bugzilla-2.16.7/enter_bug.cgi"

1848

1789

TARGET="_top"

1849

1790

> Enter a new bug report</A

1850

1791

>.

1869

1810

></DIV

1870

1811

><DIV

1871

1812

CLASS="section"

1872

><HR><H1

1813

><HR><H2

1873

1814

CLASS="section"

1874

1815

><A

1875

1816

NAME="hintsandtips"

1876

></A

1877

>3.2. Hints and Tips</H1

1817

>3.2. Hints and Tips</A

1818

></H2

1878

1819

><P

1879

1820

>This section distills some Bugzilla tips and best practices

1880

1821

that have been developed.</P

1881

1822

><DIV

1882

1823

CLASS="section"

1883

><HR><H2

1824

><HR><H3

1884

1825

CLASS="section"

1885

1826

><A

1886

1827

NAME="AEN372"

1887

></A

1888

>3.2.1. Autolinkification</H2

1828

>3.2.1. Autolinkification</A

1829

></H3

1889

1830

><P

1890

1831

>Bugzilla comments are plain text - so posting HTML will result

1891

1832

in literal HTML tags rather than being interpreted by a browser.

1945

1886

></DIV

1946

1887

><DIV

1947

1888

CLASS="section"

1948

><HR><H2

1889

><HR><H3

1949

1890

CLASS="section"

1950

1891

><A

1951

1892

NAME="quicksearch"

1952

></A

1953

>3.2.2. Quicksearch</H2

1893

>3.2.2. Quicksearch</A

1894

></H3

1954

1895

><P

1955

1896

>Quicksearch is a single-text-box query tool which uses

1956

1897

metacharacters to indicate what is to be searched. For example, typing

1978

1919

></DIV

1979

1920

><DIV

1980

1921

CLASS="section"

1981

><HR><H2

1922

><HR><H3

1982

1923

CLASS="section"

1983

1924

><A

1984

1925

NAME="commenting"

1985

></A

1986

>3.2.3. Comments</H2

1926

>3.2.3. Comments</A

1927

></H3

1987

1928

><P

1988

1929

>If you are changing the fields on a bug, only comment if

1989

1930

either you have something pertinent to say, or Bugzilla requires it.

2002

1943

></DIV

2003

1944

><DIV

2004

1945

CLASS="section"

2005

><HR><H2

1946

><HR><H3

2006

1947

CLASS="section"

2007

1948

><A

2008

1949

NAME="attachments"

2009

></A

2010

>3.2.4. Attachments</H2

1950

>3.2.4. Attachments</A

1951

></H3

2011

1952

><P

2012

1953

> Use attachments, rather than comments, for large chunks of ASCII data,

2013

1954

such as trace, debugging output files, or log files. That way, it doesn't

2028

1969

></DIV

2029

1970

><DIV

2030

1971

CLASS="section"

2031

><HR><H2

1972

><HR><H3

2032

1973

CLASS="section"

2033

1974

><A

2034

1975

NAME="AEN401"

2035

></A

2036

>3.2.5. Filing Bugs</H2

1976

>3.2.5. Filing Bugs</A

1977

></H3

2037

1978

><P

2038

1979

>Try to make sure that everything said in the summary is also

2039

1980

said in the first comment. Summaries are often updated and this will

2054

1995

></DIV

2055

1996

><DIV

2056

1997

CLASS="section"

2057

><HR><H1

1998

><HR><H2

2058

1999

CLASS="section"

2059

2000

><A

2060

2001

NAME="userpreferences"

2061

></A

2062

>3.3. User Preferences</H1

2002

>3.3. User Preferences</A

2003

></H2

2063

2004

><P

2064

2005

>Once you have logged in, you can customise various aspects of

2065

2006

Bugzilla via the "Edit prefs" link in the page footer.

2066

2007

The preferences are split into four tabs:</P

2067

2008

><DIV

2068

2009

CLASS="section"

2069

><HR><H2

2010

><HR><H3

2070

2011

CLASS="section"

2071

2012

><A

2072

2013

NAME="accountsettings"

2073

></A

2074

>3.3.1. Account Settings</H2

2014

>3.3.1. Account Settings</A

2015

></H3

2075

2016

><P

2076

2017

>On this tab, you can change your basic account information,

2077

2018

including your password, email address and real name. For security

2091

2032

></DIV

2092

2033

><DIV

2093

2034

CLASS="section"

2094

><HR><H2

2035

><HR><H3

2095

2036

CLASS="section"

2096

2037

><A

2097

2038

NAME="emailsettings"

2098

></A

2099

>3.3.2. Email Settings</H2

2039

>3.3.2. Email Settings</A

2040

></H3

2100

2041

><P

2101

2042

>On this tab you can reduce or increase the amount of email sent

2102

2043

you from Bugzilla, opting in our out depending on your relationship to

2140

2081

></DIV

2141

2082

><DIV

2142

2083

CLASS="section"

2143

><HR><H2

2084

><HR><H3

2144

2085

CLASS="section"

2145

2086

><A

2146

2087

NAME="footersettings"

2147

></A

2148

>3.3.3. Page Footer</H2

2088

>3.3.3. Page Footer</A

2089

></H3

2149

2090

><P

2150

2091

>On the Search page, you can store queries in Bugzilla, so if you

2151

2092

regularly run a particular query it is just a drop-down menu away.

2154

2095

></DIV

2155

2096

><DIV

2156

2097

CLASS="section"

2157

><HR><H2

2098

><HR><H3

2158

2099

CLASS="section"

2159

2100

><A

2160

2101

NAME="permissionsettings"

2161

></A

2162

>3.3.4. Permissions</H2

2102

>3.3.4. Permissions</A

2103

></H3

2163

2104

><P

2164

2105

>This is a purely informative page which outlines your current

2165

2106

permissions on this installation of Bugzilla - what product groups you

2177

2118

>Chapter 4. Installation</H1

2178

2119

><DIV

2179

2120

CLASS="section"

2180

><H1

2121

><H2

2181

2122

CLASS="section"

2182

2123

><A

2183

2124

NAME="stepbystep"

2184

></A

2185

>4.1. Step-by-step Install</H1

2125

>4.1. Step-by-step Install</A

2126

></H2

2186

2127

><DIV

2187

2128

CLASS="section"

2188

><H2

2129

><H3

2189

2130

CLASS="section"

2190

2131

><A

2191

2132

NAME="AEN430"

2192

></A

2193

>4.1.1. Introduction</H2

2133

>4.1.1. Introduction</A

2134

></H3

2194

2135

><P

2195

2136

>Bugzilla has been successfully installed under Solaris, Linux,

2196

2137

and Win32. Win32 is not yet officially supported, but many people

2205

2146

></DIV

2206

2147

><DIV

2207

2148

CLASS="section"

2208

><HR><H2

2149

><HR><H3

2209

2150

CLASS="section"

2210

2151

><A

2211

2152

NAME="AEN434"

2212

></A

2213

>4.1.2. Package List</H2

2153

>4.1.2. Package List</A

2154

></H3

2214

2155

><DIV

2215

2156

CLASS="note"

2216

2157

><P

2508

2449

><TBODY

2509

2450

><TR

2510

2451

><TD

2511

> <TT

2452

> <SAMP

2512

2453

CLASS="prompt"

2513

>bash#</TT

2454

>bash#</SAMP

2514

2455

>

2515

2456

2516

2457

<B

2521

2462

></TR

2522

2463

><TR

2523

2464

><TD

2524

> <TT

2465

> <SAMP

2525

2466

CLASS="prompt"

2526

>bash#</TT

2467

>bash#</SAMP

2527

2468

>

2528

2469

2529

2470

<B

2534

2475

></TR

2535

2476

><TR

2536

2477

><TD

2537

> <TT

2478

> <SAMP

2538

2479

CLASS="prompt"

2539

>bash#</TT

2480

>bash#</SAMP

2540

2481

>

2541

2482

2542

2483

<B

2547

2488

></TR

2548

2489

><TR

2549

2490

><TD

2550

> <TT

2491

> <SAMP

2551

2492

CLASS="prompt"

2552

>bash#</TT

2493

>bash#</SAMP

2553

2494

>

2554

2495

2555

2496

<B

2561

2502

></TR

2562

2503

><TR

2563

2504

><TD

2564

> <TT

2505

> <SAMP

2565

2506

CLASS="prompt"

2566

>bash#</TT

2507

>bash#</SAMP

2567

2508

>

2568

2509

2569

2510

<B

2585

2526

></DIV

2586

2527

><DIV

2587

2528

CLASS="section"

2588

><HR><H2

2529

><HR><H3

2589

2530

CLASS="section"

2590

2531

><A

2591

2532

NAME="install-mysql"

2592

></A

2593

>4.1.3. MySQL</H2

2533

>4.1.3. MySQL</A

2534

></H3

2594

2535

><P

2595

2536

>Visit the MySQL homepage at

2596

2537

<A

2661

2602

>

2662

2603

only accepts packets up to 64K long. This limits the size of

2663

2604

attachments you may put on bugs. If you add

2664

<TT

2605

<VAR

2665

2606

CLASS="option"

2666

>-O max_allowed_packet=1M</TT

2607

>-O max_allowed_packet=1M</VAR

2667

2608

>

2668

2609

to the command that starts

2669

2610

<TT

2680

2621

><P

2681

2622

>If you plan on running Bugzilla and MySQL on the same machine,

2682

2623

consider using the

2683

<TT

2624

<VAR

2684

2625

CLASS="option"

2685

>--skip-networking</TT

2626

>--skip-networking</VAR

2686

2627

>

2687

2628

option in the init script. This enhances security by preventing

2688

2629

network access to MySQL.</P

2689

2630

></DIV

2690

2631

><DIV

2691

2632

CLASS="section"

2692

><HR><H2

2633

><HR><H3

2693

2634

CLASS="section"

2694

2635

><A

2695

2636

NAME="install-perl"

2696

></A

2697

>4.1.4. Perl</H2

2637

>4.1.4. Perl</A

2638

></H3

2698

2639

><P

2699

2640

>Any machine that doesn't have Perl on it is a sad machine indeed.

2700

2641

Perl can be got in source form from

2749

2690

>,

2750

2691

which installs all required modules for you.</P

2751

2692

><P

2752

> <TT

2693

> <SAMP

2753

2694

CLASS="computeroutput"

2754

> <TT

2695

> <SAMP

2755

2696

CLASS="prompt"

2756

>bash#</TT

2697

>bash#</SAMP

2757

2698

>

2758

2699

2759

2700

<B

2760

2701

CLASS="command"

2761

2702

>perl -MCPAN -e 'install "Bundle::Bugzilla"'</B

2762

2703

>

2763

</TT

2704

</SAMP

2764

2705

>

2765

2706

</P

2766

2707

><P

2775

2716

></DIV

2776

2717

><DIV

2777

2718

CLASS="section"

2778

><HR><H2

2719

><HR><H3

2779

2720

CLASS="section"

2780

2721

><A

2781

2722

NAME="perl-modules"

2782

></A

2783

>4.1.5. Perl Modules</H2

2723

>4.1.5. Perl Modules</A

2724

></H3

2784

2725

><P

2785

2726

>

2786

2727

All Perl modules can be found on the

2799

2740

To use the CPAN shell to install a module:

2800

2741

</P

2801

2742

><P

2802

> <TT

2743

> <SAMP

2803

2744

CLASS="computeroutput"

2804

> <TT

2745

> <SAMP

2805

2746

CLASS="prompt"

2806

>bash#</TT

2747

>bash#</SAMP

2807

2748

>

2808

2749

<B

2809

2750

CLASS="command"

2810

2751

>perl -MCPAN -e 'install "<modulename>"'</B

2811

2752

>

2812

</TT

2753

</SAMP

2813

2754

>

2814

2755

</P

2815

2756

><P

2827

2768

TYPE="1"

2828

2769

><LI

2829

2770

><P

2830

> <TT

2771

> <SAMP

2831

2772

CLASS="computeroutput"

2832

> <TT

2773

> <SAMP

2833

2774

CLASS="prompt"

2834

>bash#</TT

2775

>bash#</SAMP

2835

2776

>

2836

2777

2837

2778

<B

2838

2779

CLASS="command"

2839

2780

>perl Makefile.PL</B

2840

2781

>

2841

</TT

2782

</SAMP

2842

2783

>

2843

2784

</P

2844

2785

></LI

2845

2786

><LI

2846

2787

><P

2847

> <TT

2788

> <SAMP

2848

2789

CLASS="computeroutput"

2849

> <TT

2790

> <SAMP

2850

2791

CLASS="prompt"

2851

>bash#</TT

2792

>bash#</SAMP

2852

2793

>

2853

2794

2854

2795

<B

2855

2796

CLASS="command"

2856

2797

>make</B

2857

2798

>

2858

</TT

2799

</SAMP

2859

2800

>

2860

2801

</P

2861

2802

></LI

2862

2803

><LI

2863

2804

><P

2864

> <TT

2805

> <SAMP

2865

2806

CLASS="computeroutput"

2866

> <TT

2807

> <SAMP

2867

2808

CLASS="prompt"

2868

>bash#</TT

2809

>bash#</SAMP

2869

2810

>

2870

2811

2871

2812

<B

2872

2813

CLASS="command"

2873

2814

>make test</B

2874

2815

>

2875

</TT

2816

</SAMP

2876

2817

>

2877

2818

</P

2878

2819

></LI

2879

2820

><LI

2880

2821

><P

2881

> <TT

2822

> <SAMP

2882

2823

CLASS="computeroutput"

2883

> <TT

2824

> <SAMP

2884

2825

CLASS="prompt"

2885

>bash#</TT

2826

>bash#</SAMP

2886

2827

>

2887

2828

2888

2829

<B

2889

2830

CLASS="command"

2890

2831

>make install</B

2891

2832

>

2892

</TT

2833

</SAMP

2893

2834

>

2894

2835

</P

2895

2836

></LI

2940

2881

></DIV

2941

2882

><DIV

2942

2883

CLASS="section"

2943

><HR><H3

2884

><HR><H4

2944

2885

CLASS="section"

2945

2886

><A

2946

2887

NAME="AEN580"

2947

></A

2948

>4.1.5.1. DBI</H3

2888

>4.1.5.1. DBI</A

2889

></H4

2949

2890

><P

2950

2891

>The DBI module is a generic Perl module used the

2951

2892

MySQL-related modules. As long as your Perl installation was done

2955

2896

></DIV

2956

2897

><DIV

2957

2898

CLASS="section"

2958

><HR><H3

2899

><HR><H4

2959

2900

CLASS="section"

2960

2901

><A

2961

2902

NAME="AEN583"

2962

></A

2963

>4.1.5.2. Data::Dumper</H3

2903

>4.1.5.2. Data::Dumper</A

2904

></H4

2964

2905

><P

2965

2906

>The Data::Dumper module provides data structure persistence for

2966

2907

Perl (similar to Java's serialization). It comes with later

2969

2910

></DIV

2970

2911

><DIV

2971

2912

CLASS="section"

2972

><HR><H3

2913

><HR><H4

2973

2914

CLASS="section"

2974

2915

><A

2975

2916

NAME="AEN586"

2976

></A

2977

>4.1.5.3. MySQL-related modules</H3

2917

>4.1.5.3. MySQL-related modules</A

2918

></H4

2978

2919

><P

2979

2920

>The Perl/MySQL interface requires a few mutually-dependent Perl

2980

2921

modules. These modules are grouped together into the the

2995

2936

></DIV

2996

2937

><DIV

2997

2938

CLASS="section"

2998

><HR><H3

2939

><HR><H4

2999

2940

CLASS="section"

3000

2941

><A

3001

2942

NAME="AEN591"

3002

></A

3003

>4.1.5.4. TimeDate modules</H3

2943

>4.1.5.4. TimeDate modules</A

2944

></H4

3004

2945

><P

3005

2946

>Many of the more common date/time/calendar related Perl modules

3006

2947

have been grouped into a bundle similar to the MySQL modules bundle.

3011

2952

></DIV

3012

2953

><DIV

3013

2954

CLASS="section"

3014

><HR><H3

2955

><HR><H4

3015

2956

CLASS="section"

3016

2957

><A

3017

2958

NAME="AEN594"

3018

></A

3019

>4.1.5.5. GD (optional)</H3

2959

>4.1.5.5. GD (optional)</A

2960

></H4

3020

2961

><P

3021

2962

>The GD library was written by Thomas Boutell a long while ago to

3022

2963

programatically generate images in C. Since then it's become the

3047

2988

><P

3048

2989

>The Perl GD library requires some other libraries that may or

3049

2990

may not be installed on your system, including

3050

<TT

2991

<CODE

3051

2992

CLASS="classname"

3052

>libpng</TT

2993

>libpng</CODE

3053

2994

>

3054

2995

and

3055

<TT

2996

<CODE

3056

2997

CLASS="classname"

3057

>libgd</TT

2998

>libgd</CODE

3058

2999

>.

3059

3000

The full requirements are listed in the Perl GD library README.

3060

3001

If compiling GD fails, it's probably because you're

3066

3007

></DIV

3067

3008

><DIV

3068

3009

CLASS="section"

3069

><HR><H3

3010

><HR><H4

3070

3011

CLASS="section"

3071

3012

><A

3072

3013

NAME="AEN601"

3073

></A

3074

>4.1.5.6. Chart::Base (optional)</H3

3014

>4.1.5.6. Chart::Base (optional)</A

3015

></H4

3075

3016

><P

3076

3017

>The Chart module provides Bugzilla with on-the-fly charting

3077

3018

abilities. It can be installed in the usual fashion after it has been

3081

3022

></DIV

3082

3023

><DIV

3083

3024

CLASS="section"

3084

><HR><H3

3025

><HR><H4

3085

3026

CLASS="section"

3086

3027

><A

3087

3028

NAME="AEN604"

3088

></A

3089

>4.1.5.7. Template Toolkit</H3

3029

>4.1.5.7. Template Toolkit</A

3030

></H4

3090

3031

><P

3091

3032

>When you install Template Toolkit, you'll get asked various

3092

3033

questions about features to enable. The defaults are fine, except

3099

3040

></DIV

3100

3041

><DIV

3101

3042

CLASS="section"

3102

><HR><H2

3043

><HR><H3

3103

3044

CLASS="section"

3104

3045

><A

3105

3046

NAME="AEN607"

3106

></A

3107

>4.1.6. HTTP Server</H2

3047

>4.1.6. HTTP Server</A

3048

></H3

3108

3049

><P

3109

3050

>You have a freedom of choice here - Apache, Netscape or any other

3110

3051

server on UNIX would do. You can run the web server on a

3277

3218

></DIV

3278

3219

><DIV

3279

3220

CLASS="section"

3280

><HR><H2

3221

><HR><H3

3281

3222

CLASS="section"

3282

3223

><A

3283

3224

NAME="AEN626"

3284

></A

3285

>4.1.7. Bugzilla</H2

3225

>4.1.7. Bugzilla</A

3226

></H3

3286

3227

><P

3287

3228

>You should untar the Bugzilla files into a directory that you're

3288

3229

willing to make writable by the default web server user (probably

3390

3331

></DIV

3391

3332

><DIV

3392

3333

CLASS="section"

3393

><HR><H2

3334

><HR><H3

3394

3335

CLASS="section"

3395

3336

><A

3396

3337

NAME="AEN643"

3397

></A

3398

>4.1.8. Setting Up the MySQL Database</H2

3338

>4.1.8. Setting Up the MySQL Database</A

3339

></H3

3399

3340

><P

3400

3341

>After you've gotten all the software installed and working you're

3401

3342

ready to start preparing the database for its life as the back end to

3419

3360

><TBODY

3420

3361

><TR

3421

3362

><TD

3422

> <TT

3363

> <SAMP

3423

3364

CLASS="computeroutput"

3424

> <TT

3365

> <SAMP

3425

3366

CLASS="prompt"

3426

>bash#</TT

3367

>bash#</SAMP

3427

3368

>

3428

3369

3429

3370

<B

3430

3371

CLASS="command"

3431

3372

>mysql -u root mysql</B

3432

3373

>

3433

</TT

3374

</SAMP

3434

3375

>

3435

3376

</TD

3436

3377

></TR

3437

3378

><TR

3438

3379

><TD

3439

> <TT

3380

> <SAMP

3440

3381

CLASS="computeroutput"

3441

> <TT

3382

> <SAMP

3442

3383

CLASS="prompt"

3443

>mysql></TT

3384

>mysql></SAMP

3444

3385

>

3445

3386

3446

3387

<B

3448

3389

>UPDATE user SET Password=PASSWORD('<new_password>')

3449

3390

WHERE user='root';</B

3450

3391

>

3451

</TT

3392

</SAMP

3452

3393

>

3453

3394

</TD

3454

3395

></TR

3455

3396

><TR

3456

3397

><TD

3457

> <TT

3398

> <SAMP

3458

3399

CLASS="computeroutput"

3459

> <TT

3400

> <SAMP

3460

3401

CLASS="prompt"

3461

>mysql></TT

3402

>mysql></SAMP

3462

3403

>

3463

3404

3464

3405

<B

3465

3406

CLASS="command"

3466

3407

>FLUSH PRIVILEGES;</B

3467

3408

>

3468

</TT

3409

</SAMP

3469

3410

>

3470

3411

</TD

3471

3412

></TR

3512

3453

Modify it to reflect your setup if you will be connecting from

3513

3454

another machine or as a different user.</P

3514

3455

><P

3515

>Remember to set <bugs_password> to some unique password.

3456

>Remember to set <bugs_password> to some unique password.</P

3457

><P

3458

>If you are using MySQL 4.0 or newer, enter:

3516

3459

<P

3517

3460

></P

3518

3461

><TABLE

3520

3463

><TBODY

3521

3464

><TR

3522

3465

><TD

3523

> <TT

3466

> <SAMP

3524

3467

CLASS="computeroutput"

3525

> <TT

3468

> <SAMP

3526

3469

CLASS="prompt"

3527

>mysql></TT

3470

>mysql></SAMP

3528

3471

>

3529

3472

3530

3473

<B

3531

3474

CLASS="command"

3532

3475

>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,

3533

ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost

3476

ALTER,CREATE,DROP,LOCK TABLES,CREATE TEMPORARY

3477

TABLES,REFERENCES ON bugs.* TO bugs@localhost

3534

3478

IDENTIFIED BY '<bugs_password>';</B

3535

3479

>

3536

</TT

3480

</SAMP

3537

3481

>

3538

3482

</TD

3539

3483

></TR

3540

3484

><TR

3541

3485

><TD

3542

> <TT

3486

> <SAMP

3543

3487

CLASS="computeroutput"

3544

> <TT

3488

> <SAMP

3545

3489

CLASS="prompt"

3546

>mysql></TT

3490

>mysql></SAMP

3547

3491

>

3548

3492

3549

3493

<B

3550

3494

CLASS="command"

3551

3495

>FLUSH PRIVILEGES;</B

3552

3496

>

3553

</TT

3497

</SAMP

3554

3498

>

3555

3499

</TD

3556

3500

></TR

3560

3504

></P

3561

3505

>

3562

3506

</P

3563

><DIV

3564

CLASS="note"

3565

3507

><P

3508

>If you are using an older version of MySQL,

3509

the LOCK TABLES and CREATE TEMPORARY TABLES permissions

3510

need to be removed from the list:

3511

<P

3566

3512

></P

3567

3513

><TABLE

3568

CLASS="note"

3569

WIDTH="100%"

3570

3514

BORDER="0"

3571

><TR

3572

><TD

3573

WIDTH="25"

3574

ALIGN="CENTER"

3575

VALIGN="TOP"

3576

><IMG

3577

SRC="../images/note.gif"

3578

HSPACE="5"

3579

ALT="Note"></TD

3580

><TD

3581

ALIGN="LEFT"

3582

VALIGN="TOP"

3515

><TBODY

3516

><TR

3517

><TD

3518

> <SAMP

3519

CLASS="computeroutput"

3520

> <SAMP

3521

CLASS="prompt"

3522

>mysql></SAMP

3523

>

3524

3525

<B

3526

CLASS="command"

3527

>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,

3528

ALTER,CREATE,DROP,REFERENCES ON bugs.* TO bugs@localhost

3529

IDENTIFIED BY '<bugs_password>';</B

3530

>

3531

</SAMP

3532

>

3533

</TD

3534

></TR

3535

><TR

3536

><TD

3537

> <SAMP

3538

CLASS="computeroutput"

3539

> <SAMP

3540

CLASS="prompt"

3541

>mysql></SAMP

3542

>

3543

3544

<B

3545

CLASS="command"

3546

>FLUSH PRIVILEGES;</B

3547

>

3548

</SAMP

3549

>

3550

</TD

3551

></TR

3552

></TBODY

3553

></TABLE

3583

3554

><P

3584

>If you are using MySQL 4, the bugs user also needs to be granted

3585

the LOCK TABLES and CREATE TEMPORARY TABLES permissions.

3586

</P

3587

></TD

3588

></TR

3589

></TABLE

3590

></DIV

3555

></P

3556

>

3557

</P

3591

3558

></DIV

3592

3559

><DIV

3593

3560

CLASS="section"

3594

><HR><H2

3561

><HR><H3

3595

3562

CLASS="section"

3596

3563

><A

3597

NAME="AEN681"

3598

></A

3564

NAME="AEN690"

3599

3565

>4.1.9. <TT

3600

3566

CLASS="filename"

3601

3567

>checksetup.pl</TT

3602

></H2

3568

></A

3569

></H3

3603

3570

><P

3604

3571

>Next, run the magic checksetup.pl script. (Many thanks to

3605

3572

<A

3624

3591

><TBODY

3625

3592

><TR

3626

3593

><TD

3627

> <TT

3594

> <SAMP

3628

3595

CLASS="computeroutput"

3629

> <TT

3596

> <SAMP

3630

3597

CLASS="prompt"

3631

>bash#</TT

3598

>bash#</SAMP

3632

3599

>

3633

3600

3634

3601

<B

3635

3602

CLASS="command"

3636

3603

>./checksetup.pl</B

3637

3604

>

3638

</TT

3605

</SAMP

3639

3606

>

3640

3607

</TD

3641

3608

></TR

3744

3711

></DIV

3745

3712

><DIV

3746

3713

CLASS="section"

3747

><HR><H2

3748

CLASS="section"

3749

><A

3750

NAME="AEN713"

3751

></A

3752

>4.1.10. Configuring Bugzilla</H2

3714

><HR><H3

3715

CLASS="section"

3716

><A

3717

NAME="AEN722"

3718

>4.1.10. Mail Transfer Agent (MTA)</A

3719

></H3

3720

><P

3721

>Bugzilla is dependent on the availability of an e-mail system for its user

3722

authentication and for other tasks. </P

3723

><P

3724

>On Linux, any Sendmail-compatible MTA (Mail Transfer Agent) will suffice.

3725

Sendmail, Postfix, qmail and Exim are examples of common MTAs. Sendmail is the

3726

original Unix MTA, but the others are easier to configure, and therefore many people

3727

replace Sendmail with Postfix or Exim. They are drop-in replacements, so that Bugzilla

3728

will not distinguish between them.</P

3729

><P

3730

>Consult the manual for the specific MTA you choose for detailed installation

3731

instructions. Each of these programs will have their own configuration files where you must

3732

configure certain parameters to ensure that the mail is delivered properly. They

3733

are implemented as services, and you should ensure that the MTA is in the

3734

auto-start list of services for the machine.</P

3735

><P

3736

>If a simple mail sent with the command-line 'mail' program succeeds, then

3737

Bugzilla should also be fine.</P

3738

></DIV

3739

><DIV

3740

CLASS="section"

3741

><HR><H3

3742

CLASS="section"

3743

><A

3744

NAME="AEN728"

3745

>4.1.11. Configuring Bugzilla</A

3746

></H3

3753

3747

><P

3754

3748

> You should run through the parameters on the Edit Parameters page

3755

3749

(link in the footer) and set them all to appropriate values.

3762

3756

></DIV

3763

3757

><DIV

3764

3758

CLASS="section"

3765

><HR><H1

3759

><HR><H2

3766

3760

CLASS="section"

3767

3761

><A

3768

3762

NAME="extraconfig"

3769

></A

3770

>4.2. Optional Additional Configuration</H1

3763

>4.2. Optional Additional Configuration</A

3764

></H2

3771

3765

><DIV

3772

3766

CLASS="section"

3773

><H2

3767

><H3

3774

3768

CLASS="section"

3775

3769

><A

3776

NAME="AEN719"

3777

></A

3778

>4.2.1. Dependency Charts</H2

3770

NAME="AEN734"

3771

>4.2.1. Dependency Charts</A

3772

></H3

3779

3773

><P

3780

3774

>As well as the text-based dependency graphs, Bugzilla also

3781

3775

supports dependency graphing, using a package called 'dot'.

3834

3828

></DIV

3835

3829

><DIV

3836

3830

CLASS="section"

3837

><HR><H2

3831

><HR><H3

3838

3832

CLASS="section"

3839

3833

><A

3840

NAME="AEN734"

3841

></A

3842

>4.2.2. Bug Graphs</H2

3834

NAME="AEN749"

3835

>4.2.2. Bug Graphs</A

3836

></H3

3843

3837

><P

3844

3838

>As long as you installed the GD and Graph::Base Perl modules you

3845

3839

might as well turn on the nifty Bugzilla bug reporting graphs.</P

3857

3851

><TBODY

3858

3852

><TR

3859

3853

><TD

3860

> <TT

3854

> <SAMP

3861

3855

CLASS="computeroutput"

3862

> <TT

3856

> <SAMP

3863

3857

CLASS="prompt"

3864

>bash#</TT

3858

>bash#</SAMP

3865

3859

>

3866

3860

3867

3861

<B

3868

3862

CLASS="command"

3869

3863

>crontab -e</B

3870

3864

>

3871

</TT

3865

</SAMP

3872

3866

>

3873

3867

</TD

3874

3868

></TR

3875

3869

><TR

3876

3870

><TD

3877

> <TT

3871

> <SAMP

3878

3872

CLASS="computeroutput"

3879

3873

>5 0 * * * cd <your-bugzilla-directory> ;

3880

./collectstats.pl</TT

3874

./collectstats.pl</SAMP

3881

3875

>

3882

3876

</TD

3883

3877

></TR

3893

3887

></DIV

3894

3888

><DIV

3895

3889

CLASS="section"

3896

><HR><H2

3890

><HR><H3

3897

3891

CLASS="section"

3898

3892

><A

3899

NAME="AEN747"

3900

></A

3901

>4.2.3. The Whining Cron</H2

3893

NAME="AEN762"

3894

>4.2.3. The Whining Cron</A

3895

></H3

3902

3896

><P

3903

3897

>By now you have a fully functional Bugzilla, but what good are

3904

3898

bugs if they're not annoying? To help make those bugs more annoying you

3916

3910

><TBODY

3917

3911

><TR

3918

3912

><TD

3919

> <TT

3913

> <SAMP

3920

3914

CLASS="computeroutput"

3921

3915

> <B

3922

3916

CLASS="command"

3923

3917

>cd <your-bugzilla-directory> ;

3924

3918

./whineatnews.pl</B

3925

3919

>

3926

</TT

3920

</SAMP

3927

3921

>

3928

3922

</TD

3929

3923

></TR

3981

3975

></DIV

3982

3976

><DIV

3983

3977

CLASS="section"

3984

><HR><H2

3978

><HR><H3

3985

3979

CLASS="section"

3986

3980

><A

3987

3981

NAME="bzldap"

3988

></A

3989

>4.2.4. LDAP Authentication</H2

3982

>4.2.4. LDAP Authentication</A

3983

></H3

3990

3984

><P

3991

3985

> <DIV

3992

3986

CLASS="warning"

4074

4068

></DIV

4075

4069

><DIV

4076

4070

CLASS="section"

4077

><HR><H2

4071

><HR><H3

4078

4072

CLASS="section"

4079

4073

><A

4080

4074

NAME="content-type"

4081

></A

4082

4075

>4.2.5. Preventing untrusted Bugzilla content from executing malicious

4083

Javascript code</H2

4076

Javascript code</A

4077

></H3

4084

4078

><P

4085

4079

>It is possible for a Bugzilla to execute malicious Javascript

4086

4080

code. Due to internationalization concerns, we are unable to

4146

4140

></DIV

4147

4141

><DIV

4148

4142

CLASS="section"

4149

><HR><H2

4143

><HR><H3

4150

4144

CLASS="section"

4151

4145

><A

4152

4146

NAME="htaccess"

4153

></A

4154

4147

>4.2.6. <TT

4155

4148

CLASS="filename"

4156

4149

>.htaccess</TT

4157

4150

>

4158

files and security</H2

4151

files and security</A

4152

></H3

4159

4153

><P

4160

4154

>To enhance the security of your Bugzilla installation, Bugzilla's

4161

4155

<TT

4303

4297

>localconfig</TT

4304

4298

>

4305

4299

and setting the

4306

<TT

4300

<VAR

4307

4301

CLASS="varname"

4308

>$create_htaccess</TT

4302

>$create_htaccess</VAR

4309

4303

>

4310

4304

variable to

4311

<TT

4305

<VAR

4312

4306

CLASS="parameter"

4313

><I

4314

>0</I

4315

></TT

4307

>0</VAR

4316

4308

>.

4317

4309

</P

4318

4310

></DIV

4319

4311

><DIV

4320

4312

CLASS="section"

4321

><HR><H2

4313

><HR><H3

4322

4314

CLASS="section"

4323

4315

><A

4324

4316

NAME="mod-throttle"

4325

></A

4326

4317

>4.2.7. <TT

4327

4318

CLASS="filename"

4328

4319

>mod_throttle</TT

4329

4320

>

4330

4321

4331

and Security</H2

4322

and Security</A

4323

></H3

4332

4324

><P

4333

4325

>It is possible for a user, by mistake or on purpose, to access

4334

4326

the database many times in a row which can result in very slow access

4369

4361

></DIV

4370

4362

><DIV

4371

4363

CLASS="section"

4372

><HR><H1

4364

><HR><H2

4373

4365

CLASS="section"

4374

4366

><A

4375

4367

NAME="win32"

4376

></A

4377

>4.3. Win32 Installation Notes</H1

4368

>4.3. Win32 Installation Notes</A

4369

></H2

4378

4370

><P

4379

4371

>This section covers installation on Microsoft Windows.

4380

4372

Bugzilla has been made to work on Win32 platforms, but the Bugzilla team

4431

4423

>.

4432

4424

After that, you'll need to read the (outdated) installation

4433

4425

instructions below, some (probably a lot better) <A

4434

HREF="http://bugzilla.mozilla.org/attachment.cgi?id=84430&action=view"

4426

HREF="http://bugzilla.mozilla.org/attachment.cgi?id=84430&action=view"

4435

4427

TARGET="_top"

4436

4428

>more

4437

4429

recent ones</A

4448

4440

</P

4449

4441

><DIV

4450

4442

CLASS="section"

4451

><HR><H2

4443

><HR><H3

4452

4444

CLASS="section"

4453

4445

><A

4454

4446

NAME="wininstall"

4455

></A

4456

>4.3.1. Win32 Installation: Step-by-step</H2

4447

>4.3.1. Win32 Installation: Step-by-step</A

4448

></H3

4457

4449

><DIV

4458

4450

CLASS="note"

4459

4451

><P

4671

4663

></DIV

4672

4664

><P

4673

4665

>The syntax for ppm is:

4674

<TT

4666

<SAMP

4675

4667

CLASS="computeroutput"

4676

> <TT

4668

> <SAMP

4677

4669

CLASS="prompt"

4678

>C:></TT

4670

>C:></SAMP

4679

4671

>

4680

4672

4681

4673

<B

4682

4674

CLASS="command"

4683

>ppm <modulename></B

4675

>ppm install <modulename></B

4684

4676

>

4685

</TT

4677

</SAMP

4686

4678

>

4687

4679

</P

4688

4680

><DIV

4689

4681

CLASS="example"

4690

4682

><A

4691

NAME="AEN863"

4683

NAME="AEN878"

4692

4684

></A

4693

4685

><P

4694

4686

><B

4695

4687

>Example 4-1. Installing ActivePerl ppd Modules on Microsoft

4696

4688

Windows</B

4697

4689

></P

4698

><P

4699

> <TT

4700

CLASS="prompt"

4701

>C:></TT

4702

>

4703

4704

<B

4705

CLASS="command"

4706

>ppm

4707

<TT

4708

CLASS="option"

4709

>DBD-Mysql</TT

4710

>

4711

</B

4712

>

4713

</P

4690

><TABLE

4691

BORDER="0"

4692

BGCOLOR="#E0E0E0"

4693

WIDTH="100%"

4694

><TR

4695

><TD

4696

><FONT

4697

COLOR="#000000"

4698

><PRE

4699

CLASS="programlisting"

4700

><B

4701

CLASS="command"

4702

>ppm repository add oi http://openinteract.sourceforge.net/ppmpackages</B

4703

>

4704

<B

4705

CLASS="command"

4706

>ppm install DBD-mysql</B

4707

>

4708

<B

4709

CLASS="command"

4710

>ppm install Template-Toolkit</B

4711

>

4712

<B

4713

CLASS="command"

4714

>ppm install TimeDate</B

4715

>

4716

</PRE

4717

></FONT

4718

></TD

4719

></TR

4720

></TABLE

4714

4721

><P

4715

4722

>Watch your capitalization!</P

4716

4723

></DIV

4719

4726

ppm, so you might see the following error when trying to install

4720

4727

the version at OpenInteract:</P

4721

4728

><P

4722

> <TT

4729

> <SAMP

4723

4730

CLASS="computeroutput"

4724

4731

>Error installing package 'AppConfig': Read a PPD

4725

4732

for 'AppConfig', but it is not intended for this build of Perl

4726

(MSWin32-x86-multi-thread)</TT

4733

(MSWin32-x86-multi-thread)</SAMP

4727

4734

>

4728

4735

</P

4729

4736

><P

4748

4755

<DIV

4749

4756

CLASS="example"

4750

4757

><A

4751

NAME="AEN876"

4758

NAME="AEN892"

4752

4759

></A

4753

4760

><P

4754

4761

><B

4756

4763

Windows</B

4757

4764

></P

4758

4765

><P

4759

> <TT

4766

> <SAMP

4760

4767

CLASS="computeroutput"

4761

4768

> <B

4762

4769

CLASS="command"

4767

4774

>

4768

4775

</B

4769

4776

>

4770

</TT

4777

</SAMP

4771

4778

>

4772

4779

</P

4773

4780

></DIV

4822

4829

TYPE="a"

4823

4830

><LI

4824

4831

><P

4825

> <TT

4832

> <SAMP

4826

4833

CLASS="computeroutput"

4827

> <TT

4834

> <SAMP

4828

4835

CLASS="prompt"

4829

>C:></TT

4836

>C:></SAMP

4830

4837

>

4831

4838

4832

4839

<B

4833

4840

CLASS="command"

4834

4841

>C:\mysql\bin\mysql -u root mysql</B

4835

4842

>

4836

</TT

4843

</SAMP

4837

4844

>

4838

4845

</P

4839

4846

></LI

4840

4847

><LI

4841

4848

><P

4842

> <TT

4849

> <SAMP

4843

4850

CLASS="computeroutput"

4844

> <TT

4851

> <SAMP

4845

4852

CLASS="prompt"

4846

>mysql></TT

4853

>mysql></SAMP

4847

4854

>

4848

4855

4849

4856

<B

4851

4858

>DELETE FROM user WHERE Host='localhost' AND

4852

4859

User='';</B

4853

4860

>

4854

</TT

4861

</SAMP

4855

4862

>

4856

4863

</P

4857

4864

></LI

4858

4865

><LI

4859

4866

><P

4860

> <TT

4867

> <SAMP

4861

4868

CLASS="computeroutput"

4862

> <TT

4869

> <SAMP

4863

4870

CLASS="prompt"

4864

>mysql></TT

4871

>mysql></SAMP

4865

4872

>

4866

4873

4867

4874

<B

4869

4876

>UPDATE user SET Password=PASSWORD ('new_password')

4870

4877

WHERE user='root';</B

4871

4878

>

4872

</TT

4879

</SAMP

4873

4880

>

4874

4881

</P

4875

4882

><P

4891

4898

NAME="ntbugs-password"

4892

4899

></A

4893

4900

><P

4894

> <TT

4901

> <SAMP

4895

4902

CLASS="computeroutput"

4896

> <TT

4903

> <SAMP

4897

4904

CLASS="prompt"

4898

>mysql></TT

4905

>mysql></SAMP

4899

4906

>

4900

4907

4901

4908

<B

4904

4911

ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost

4905

4912

IDENTIFIED BY 'bugs_password';</B

4906

4913

>

4907

</TT

4914

</SAMP

4908

4915

>

4909

4916

</P

4910

4917

><P

4923

4930

></LI

4924

4931

><LI

4925

4932

><P

4926

> <TT

4933

> <SAMP

4927

4934

CLASS="computeroutput"

4928

> <TT

4935

> <SAMP

4929

4936

CLASS="prompt"

4930

>mysql></TT

4937

>mysql></SAMP

4931

4938

>

4932

4939

4933

4940

<B

4934

4941

CLASS="command"

4935

4942

>FLUSH PRIVILEGES;</B

4936

4943

>

4937

</TT

4944

</SAMP

4938

4945

>

4939

4946

</P

4940

4947

></LI

4941

4948

><LI

4942

4949

><P

4943

> <TT

4950

> <SAMP

4944

4951

CLASS="computeroutput"

4945

> <TT

4952

> <SAMP

4946

4953

CLASS="prompt"

4947

>mysql></TT

4954

>mysql></SAMP

4948

4955

>

4949

4956

4950

4957

<B

4951

4958

CLASS="command"

4952

4959

>create database bugs;</B

4953

4960

>

4954

</TT

4961

</SAMP

4955

4962

>

4956

4963

</P

4957

4964

></LI

4958

4965

><LI

4959

4966

><P

4960

> <TT

4967

> <SAMP

4961

4968

CLASS="computeroutput"

4962

> <TT

4969

> <SAMP

4963

4970

CLASS="prompt"

4964

>mysql></TT

4971

>mysql></SAMP

4965

4972

>

4966

4973

4967

4974

<B

4968

4975

CLASS="command"

4969

4976

>exit;</B

4970

4977

>

4971

</TT

4978

</SAMP

4972

4979

>

4973

4980

</P

4974

4981

></LI

4975

4982

><LI

4976

4983

><P

4977

> <TT

4984

> <SAMP

4978

4985

CLASS="computeroutput"

4979

> <TT

4986

> <SAMP

4980

4987

CLASS="prompt"

4981

>C:></TT

4988

>C:></SAMP

4982

4989

>

4983

4990

4984

4991

<B

4986

4993

>C:\mysql\bin\mysqladmin -u root -p

4987

4994

reload</B

4988

4995

>

4989

</TT

4996

</SAMP

4990

4997

>

4991

4998

</P

4992

4999

></LI

5080

5087

>

5081

5088

5082

5089

to suit your requirements. Set

5083

<TT

5090

<VAR

5084

5091

CLASS="varname"

5085

>$db_pass</TT

5092

>$db_pass</VAR

5086

5093

>

5087

5094

5088

5095

to your

5098

5105

>

5099

5106

5100

5107

, and

5101

<TT

5108

<VAR

5102

5109

CLASS="varname"

5103

>$webservergroup</TT

5110

>$webservergroup</VAR

5104

5111

>

5105

5112

5106

5113

to

5138

5145

>

5139

5146

5140

5147

for

5141

<TT

5148

<VAR

5142

5149

CLASS="varname"

5143

>$webservergroup</TT

5150

>$webservergroup</VAR

5144

5151

>

5145

5152

5146

5153

above. If it's wrong, please send corrections.</P

5158

5165

>

5159

5166

5160

5167

to suit your requirements. Particularly, set

5161

<TT

5168

<VAR

5162

5169

CLASS="varname"

5163

>DefParam("maintainer")</TT

5170

>DefParam("maintainer")</VAR

5164

5171

>

5165

5172

5166

5173

and

5167

<TT

5174

<VAR

5168

5175

CLASS="varname"

5169

>DefParam("urlbase") to match your install.</TT

5176

>DefParam("urlbase") to match your install.</VAR

5170

5177

>

5171

5178

</P

5172

5179

><DIV

5322

5329

VALIGN="TOP"

5323

5330

><P

5324

5331

>Some mention to also edit

5325

<TT

5332

<VAR

5326

5333

CLASS="varname"

5327

>$db_pass</TT

5334

>$db_pass</VAR

5328

5335

>

5329

5336

5330

5337

in

5693

5700

><LI

5694

5701

><P

5695

5702

>Add

5696

<TT

5703

<CODE

5697

5704

CLASS="function"

5698

>binmode()</TT

5705

>binmode()</CODE

5699

5706

>

5700

5707

5701

5708

calls so attachments will work (

5723

5730

>

5724

5731

5725

5732

before the

5726

<TT

5733

<CODE

5727

5734

CLASS="function"

5728

>require 'CGI.pl';</TT

5735

>require 'CGI.pl';</CODE

5729

5736

>

5730

5737

5731

5738

line.</P

5780

5787

>

5781

5788

5782

5789

, the perl documentation says that you should always use

5783

<TT

5790

<CODE

5784

5791

CLASS="function"

5785

>binmode()</TT

5792

>binmode()</CODE

5786

5793

>

5787

5794

5788

5795

when dealing with binary files, but never when dealing with text

5789

5796

files. That seems to suggest that rather than arbitrarily putting

5790

5797

5791

<TT

5798

<CODE

5792

5799

CLASS="function"

5793

>binmode()</TT

5800

>binmode()</CODE

5794

5801

>

5795

5802

5796

5803

at the beginning of the attachment files, there should be logic

5797

5804

to determine if

5798

<TT

5805

<CODE

5799

5806

CLASS="function"

5800

>binmode()</TT

5807

>binmode()</CODE

5801

5808

>

5802

5809

5803

5810

is needed or not.</P

5861

5868

></DIV

5862

5869

><DIV

5863

5870

CLASS="section"

5864

><HR><H2

5871

><HR><H3

5865

5872

CLASS="section"

5866

5873

><A

5867

5874

NAME="addlwintips"

5868

></A

5869

>4.3.2. Additional Windows Tips</H2

5875

>4.3.2. Additional Windows Tips</A

5876

></H3

5870

5877

><DIV

5871

5878

CLASS="tip"

5872

5879

><P

5890

5897

><P

5891

5898

>From Andrew Pearson:

5892

5899

<A

5893

NAME="AEN1046"

5900

NAME="AEN1062"

5894

5901

></A

5895

5902

><BLOCKQUOTE

5896

5903

CLASS="BLOCKQUOTE"

5971

5978

>

5972

5979

5973

5980

for Bugzilla 2.13 and later, which includes the current release,

5974

Bugzilla 2.16.4.

5981

Bugzilla 2.16.7.

5975

5982

<DIV

5976

5983

CLASS="example"

5977

5984

><A

5978

NAME="AEN1058"

5985

NAME="AEN1074"

5979

5986

></A

5980

5987

><P

5981

5988

><B

6033

6040

></DIV

6034

6041

><DIV

6035

6042

CLASS="section"

6036

><HR><H1

6043

><HR><H2

6037

6044

CLASS="section"

6038

6045

><A

6039

6046

NAME="osx"

6040

></A

6041

>4.4. Mac OS X Installation Notes</H1

6047

>4.4. Mac OS X Installation Notes</A

6048

></H2

6042

6049

><P

6043

6050

>There are a lot of common libraries and utilities out there that

6044

6051

Apple did not include with Mac OS X, but which run perfectly well on it.

6076

6083

>"install GD"</SPAN

6077

6084

>

6078

6085

at the

6079

<TT

6086

<SAMP

6080

6087

CLASS="prompt"

6081

>cpan></TT

6088

>cpan></SAMP

6082

6089

>

6083

6090

prompt, type

6084

6091

<B

6158

6165

></DIV

6159

6166

><DIV

6160

6167

CLASS="section"

6161

><HR><H1

6168

><HR><H2

6169

CLASS="section"

6170

><A

6171

NAME="nonroot"

6172

>4.5. UNIX (non-root) Installation Notes</A

6173

></H2

6174

><DIV

6175

CLASS="section"

6176

><H3

6177

CLASS="section"

6178

><A

6179

NAME="AEN1107"

6180

>4.5.1. Introduction</A

6181

></H3

6182

><P

6183

>If you are running a *NIX OS as non-root, either due

6184

to lack of access (web hosts, for example) or for security

6185

reasons, this will detail how to install Bugzilla on such

6186

a setup. It is recommended that you read through the

6187

<A

6188

HREF="#installation"

6189

>Bugzilla Installation</A

6190

>

6191

first to get an idea on the installation steps required.

6192

(These notes will reference to steps in that guide.)</P

6193

></DIV

6194

><DIV

6195

CLASS="section"

6196

><HR><H3

6197

CLASS="section"

6198

><A

6199

NAME="AEN1111"

6200

>4.5.2. MySQL</A

6201

></H3

6202

><P

6203

>You may have MySQL installed as root. If you're

6204

setting up an account with a web host, a MySQL account

6205

needs to be set up for you. From there, you can create

6206

the bugs account, or use the account given to you.</P

6207

><DIV

6208

CLASS="warning"

6209

><P

6210

></P

6211

><TABLE

6212

CLASS="warning"

6213

WIDTH="100%"

6214

BORDER="0"

6215

><TR

6216

><TD

6217

WIDTH="25"

6218

ALIGN="CENTER"

6219

VALIGN="TOP"

6220

><IMG

6221

SRC="../images/warning.gif"

6222

HSPACE="5"

6223

ALT="Warning"></TD

6224

><TD

6225

ALIGN="LEFT"

6226

VALIGN="TOP"

6227

><P

6228

>You may have problems trying to set up

6229

<B

6230

CLASS="command"

6231

>GRANT</B

6232

> permissions to the database.

6233

If you're using a web host, chances are that you have a

6234

separate database which is already locked down (or one big

6235

database with limited/no access to the other areas), but you

6236

may want to ask your system adminstrator what the security

6237

settings are set to, and/or run the <B

6238

CLASS="command"

6239

>GRANT</B

6240

>

6241

command for you.</P

6242

><P

6243

>Also, you will probably not be able to change the MySQL

6244

root user password (for obvious reasons), so skip that

6245

step.</P

6246

></TD

6247

></TR

6248

></TABLE

6249

></DIV

6250

><DIV

6251

CLASS="section"

6252

><HR><H4

6253

CLASS="section"

6254

><A

6255

NAME="AEN1119"

6256

>4.5.2.1. Running MySQL as Non-Root</A

6257

></H4

6258

><DIV

6259

CLASS="section"

6260

><H5

6261

CLASS="section"

6262

><A

6263

NAME="AEN1121"

6264

>4.5.2.1.1. The Custom Configuration Method</A

6265

></H5

6266

><P

6267

>Create a file .my.cnf in your

6268

home directory (using /home/foo in this example)

6269

as follows....</P

6270

><TABLE

6271

BORDER="0"

6272

BGCOLOR="#E0E0E0"

6273

WIDTH="100%"

6274

><TR

6275

><TD

6276

><FONT

6277

COLOR="#000000"

6278

><PRE

6279

CLASS="programlisting"

6280

>[mysqld]

6281

datadir=/home/foo/mymysql

6282

socket=/home/foo/mymysql/thesock

6283

port=8081

6284

6285

[mysql]

6286

socket=/home/foo/mymysql/thesock

6287

port=8081

6288

6289

[mysql.server]

6290

user=mysql

6291

basedir=/var/lib

6292

6293

[safe_mysqld]

6294

err-log=/home/foo/mymysql/the.log

6295

pid-file=/home/foo/mymysql/the.pid

6296

</PRE

6297

></FONT

6298

></TD

6299

></TR

6300

></TABLE

6301

></DIV

6302

><DIV

6303

CLASS="section"

6304

><HR><H5

6305

CLASS="section"

6306

><A

6307

NAME="AEN1125"

6308

>4.5.2.1.2. The Custom Built Method</A

6309

></H5

6310

><P

6311

>You can install MySQL as a not-root, if you really need to.

6312

Build it with PREFIX set to <TT

6313

CLASS="filename"

6314

>/home/foo/mysql</TT

6315

>,

6316

or use pre-installed executables, specifying that you want

6317

to put all of the data files in <TT

6318

CLASS="filename"

6319

>/home/foo/mysql/data</TT

6320

>.

6321

If there is another MySQL server running on the system that you

6322

do not own, use the -P option to specify a TCP port that is not

6323

in use.</P

6324

></DIV

6325

><DIV

6326

CLASS="section"

6327

><HR><H5

6328

CLASS="section"

6329

><A

6330

NAME="AEN1130"

6331

>4.5.2.1.3. Starting the Server</A

6332

></H5

6333

><P

6334

>After your mysqld program is built and any .my.cnf file is

6335

in place, you must initialize the databases (ONCE).</P

6336

><TABLE

6337

BORDER="0"

6338

BGCOLOR="#E0E0E0"

6339

WIDTH="100%"

6340

><TR

6341

><TD

6342

><FONT

6343

COLOR="#000000"

6344

><PRE

6345

CLASS="screen"

6346

> <SAMP

6347

CLASS="prompt"

6348

>bash$</SAMP

6349

>

6350

<B

6351

CLASS="command"

6352

>mysql_install_db</B

6353

>

6354

</PRE

6355

></FONT

6356

></TD

6357

></TR

6358

></TABLE

6359

><P

6360

>Then start the daemon with</P

6361

><TABLE

6362

BORDER="0"

6363

BGCOLOR="#E0E0E0"

6364

WIDTH="100%"

6365

><TR

6366

><TD

6367

><FONT

6368

COLOR="#000000"

6369

><PRE

6370

CLASS="screen"

6371

> <SAMP

6372

CLASS="prompt"

6373

>bash$</SAMP

6374

>

6375

<B

6376

CLASS="command"

6377

>safe_mysql &</B

6378

>

6379

</PRE

6380

></FONT

6381

></TD

6382

></TR

6383

></TABLE

6384

><P

6385

>After you start mysqld the first time, you then connect to

6386

it as "root" and <B

6387

CLASS="command"

6388

>GRANT</B

6389

> permissions to other

6390

users. (Again, the MySQL root account has nothing to do with

6391

the *NIX root account.)</P

6392

><DIV

6393

CLASS="note"

6394

><P

6395

></P

6396

><TABLE

6397

CLASS="note"

6398

WIDTH="100%"

6399

BORDER="0"

6400

><TR

6401

><TD

6402

WIDTH="25"

6403

ALIGN="CENTER"

6404

VALIGN="TOP"

6405

><IMG

6406

SRC="../images/note.gif"

6407

HSPACE="5"

6408

ALT="Note"></TD

6409

><TD

6410

ALIGN="LEFT"

6411

VALIGN="TOP"

6412

><P

6413

>You will need to start the daemons yourself. You can either

6414

ask your system administrator to add them to system startup files, or

6415

add a crontab entry that runs a script to check on these daemons

6416

and restart them if needed.</P

6417

></TD

6418

></TR

6419

></TABLE

6420

></DIV

6421

><DIV

6422

CLASS="warning"

6423

><P

6424

></P

6425

><TABLE

6426

CLASS="warning"

6427

WIDTH="100%"

6428

BORDER="0"

6429

><TR

6430

><TD

6431

WIDTH="25"

6432

ALIGN="CENTER"

6433

VALIGN="TOP"

6434

><IMG

6435

SRC="../images/warning.gif"

6436

HSPACE="5"

6437

ALT="Warning"></TD

6438

><TD

6439

ALIGN="LEFT"

6440

VALIGN="TOP"

6441

><P

6442

>Do NOT run daemons or other services on a server without first

6443

consulting your system administrator! Daemons use up system resources

6444

and running one may be in violation of your terms of service for any

6445

machine on which you are a user!</P

6446

></TD

6447

></TR

6448

></TABLE

6449

></DIV

6450

></DIV

6451

></DIV

6452

></DIV

6453

><DIV

6454

CLASS="section"

6455

><HR><H3

6456

CLASS="section"

6457

><A

6458

NAME="AEN1146"

6459

>4.5.3. Perl</A

6460

></H3

6461

><P

6462

>On the extremely rare chance that you don't have Perl on

6463

the machine, you will have to build the sources

6464

yourself. The following commands should get your system

6465

installed with your own personal version of Perl:</P

6466

><TABLE

6467

BORDER="0"

6468

BGCOLOR="#E0E0E0"

6469

WIDTH="100%"

6470

><TR

6471

><TD

6472

><FONT

6473

COLOR="#000000"

6474

><PRE

6475

CLASS="screen"

6476

> <SAMP

6477

CLASS="prompt"

6478

>bash$</SAMP

6479

>

6480

<B

6481

CLASS="command"

6482

>wget http://perl.com/CPAN/src/stable.tar.gz</B

6483

>

6484

<SAMP

6485

CLASS="prompt"

6486

>bash$</SAMP

6487

>

6488

<B

6489

CLASS="command"

6490

>tar zvxf stable.tar.gz</B

6491

>

6492

<SAMP

6493

CLASS="prompt"

6494

>bash$</SAMP

6495

>

6496

<B

6497

CLASS="command"

6498

>cd perl-5.8.1</B

6499

> (or whatever the version of Perl is called)

6500

<SAMP

6501

CLASS="prompt"

6502

>bash$</SAMP

6503

>

6504

<B

6505

CLASS="command"

6506

>sh Configure -de -Dprefix=/home/foo/perl</B

6507

>

6508

<SAMP

6509

CLASS="prompt"

6510

>bash$</SAMP

6511

>

6512

<B

6513

CLASS="command"

6514

>make && make test && make install</B

6515

>

6516

</PRE

6517

></FONT

6518

></TD

6519

></TR

6520

></TABLE

6521

><P

6522

>Once you have Perl installed into a directory (probably

6523

in <TT

6524

CLASS="filename"

6525

>~/perl/bin</TT

6526

>), you'll have to

6527

change the locations on the scripts, which is detailed later on

6528

this page.</P

6529

></DIV

6530

><DIV

6531

CLASS="section"

6532

><HR><H3

6533

CLASS="section"

6534

><A

6535

NAME="AEN1162"

6536

>4.5.4. Perl Modules</A

6537

></H3

6538

><P

6539

>Installing the Perl modules as a non-root user is probably the

6540

hardest part of the process. There are two different methods: a

6541

completely independant Perl with its own modules, or personal

6542

modules using the current (root installed) version of Perl. The

6543

independant method takes up quite a bit of disk space, but is

6544

less complex, while the mixed method only uses as much space as the

6545

modules themselves, but takes more work to setup.</P

6546

><DIV

6547

CLASS="section"

6548

><HR><H4

6549

CLASS="section"

6550

><A

6551

NAME="AEN1165"

6552

>4.5.4.1. The Independant Method</A

6553

></H4

6554

><P

6555

>The independant method requires that you install your own

6556

personal version of Perl, as detailed in the previous section. Once

6557

installed, you can start the CPAN shell with the following

6558

command:</P

6559

><P

6560

> <TABLE

6561

BORDER="0"

6562

BGCOLOR="#E0E0E0"

6563

WIDTH="100%"

6564

><TR

6565

><TD

6566

><FONT

6567

COLOR="#000000"

6568

><PRE

6569

CLASS="screen"

6570

> <SAMP

6571

CLASS="prompt"

6572

>bash$</SAMP

6573

>

6574

<B

6575

CLASS="command"

6576

>/home/foo/perl/bin/perl -MCPAN -e 'shell'</B

6577

>

6578

</PRE

6579

></FONT

6580

></TD

6581

></TR

6582

></TABLE

6583

>

6584

</P

6585

><P

6586

>And then:</P

6587

><P

6588

> <TABLE

6589

BORDER="0"

6590

BGCOLOR="#E0E0E0"

6591

WIDTH="100%"

6592

><TR

6593

><TD

6594

><FONT

6595

COLOR="#000000"

6596

><PRE

6597

CLASS="screen"

6598

> <SAMP

6599

CLASS="prompt"

6600

>cpan></SAMP

6601

>

6602

<B

6603

CLASS="command"

6604

>install Bundle::Bugzilla</B

6605

>

6606

</PRE

6607

></FONT

6608

></TD

6609

></TR

6610

></TABLE

6611

>

6612

</P

6613

><P

6614

>With this method, module installation will usually go a lot

6615

smoother, but if you have any hang-ups, you can consult the next

6616

section.</P

6617

></DIV

6618

><DIV

6619

CLASS="section"

6620

><HR><H4

6621

CLASS="section"

6622

><A

6623

NAME="AEN1178"

6624

>4.5.4.2. The Mixed Method</A

6625

></H4

6626

><P

6627

>First, you'll need to configure CPAN to

6628

install modules in your home directory. The CPAN FAQ says the

6629

following on this issue:</P

6630

><P

6631

> <TABLE

6632

BORDER="0"

6633

BGCOLOR="#E0E0E0"

6634

WIDTH="100%"

6635

><TR

6636

><TD

6637

><FONT

6638

COLOR="#000000"

6639

><PRE

6640

CLASS="programlisting"

6641

>5) I am not root, how can I install a module in a personal directory?

6642

6643

You will most probably like something like this:

6644

6645

o conf makepl_arg "LIB=~/myperl/lib \

6646

INSTALLMAN1DIR=~/myperl/man/man1 \

6647

INSTALLMAN3DIR=~/myperl/man/man3"

6648

install Sybase::Sybperl

6649

6650

You can make this setting permanent like all "o conf" settings with "o conf commit".

6651

6652

You will have to add ~/myperl/man to the MANPATH environment variable and also tell your Perl programs to

6653

look into ~/myperl/lib, e.g. by including

6654

6655

use lib "$ENV{HOME}/myperl/lib";

6656

6657

or setting the PERL5LIB environment variable.

6658

6659

Another thing you should bear in mind is that the UNINST parameter should never be set if you are not root.</PRE

6660

></FONT

6661

></TD

6662

></TR

6663

></TABLE

6664

>

6665

</P

6666

><P

6667

>So, you will need to create a Perl directory in your home

6668

directory, as well as the <TT

6669

CLASS="filename"

6670

>lib</TT

6671

>,

6672

<TT

6673

CLASS="filename"

6674

>man</TT

6675

>,

6676

<TT

6677

CLASS="filename"

6678

>man/man1</TT

6679

>, and

6680

<TT

6681

CLASS="filename"

6682

>man/man3</TT

6683

> directories in that

6684

Perl directory. Set the MANPATH variable and PERL5LIB variable, so

6685

that the installation of the modules goes smoother. (Setting

6686

UNINST=0 in your "make install" options, on the CPAN first-time

6687

configuration, is also a good idea.)</P

6688

><P

6689

>After that, go into the CPAN shell:</P

6690

><P

6691

> <TABLE

6692

BORDER="0"

6693

BGCOLOR="#E0E0E0"

6694

WIDTH="100%"

6695

><TR

6696

><TD

6697

><FONT

6698

COLOR="#000000"

6699

><PRE

6700

CLASS="screen"

6701

> <SAMP

6702

CLASS="prompt"

6703

>bash$</SAMP

6704

>

6705

<B

6706

CLASS="command"

6707

>perl -MCPAN -e 'shell'</B

6708

>

6709

</PRE

6710

></FONT

6711

></TD

6712

></TR

6713

></TABLE

6714

>

6715

</P

6716

><P

6717

>From there, you will need to type in the above "o conf" command

6718

and commit the changes. Then you can run through the installation:</P

6719

><P

6720

> <TABLE

6721

BORDER="0"

6722

BGCOLOR="#E0E0E0"

6723

WIDTH="100%"

6724

><TR

6725

><TD

6726

><FONT

6727

COLOR="#000000"

6728

><PRE

6729

CLASS="screen"

6730

> <SAMP

6731

CLASS="prompt"

6732

>cpan></SAMP

6733

>

6734

<B

6735

CLASS="command"

6736

>install Bundle::Bugzilla</B

6737

>

6738

</PRE

6739

></FONT

6740

></TD

6741

></TR

6742

></TABLE

6743

>

6744

</P

6745

><P

6746

>Most of the module installation process should go smoothly. However,

6747

you may have some problems with Template. When you first start, you will

6748

want to try to install Template with the XS Stash options on. If this

6749

doesn't work, it may spit out C compiler error messages and croak back

6750

to the CPAN shell prompt. So, redo the install, and turn it off. (In fact,

6751

say no to all of the Template questions.) It may also start failing on a

6752

few of the tests. If the total tests passed is a reasonable figure (90+%),

6753

force the install with the following command:</P

6754

><P

6755

> <TABLE

6756

BORDER="0"

6757

BGCOLOR="#E0E0E0"

6758

WIDTH="100%"

6759

><TR

6760

><TD

6761

><FONT

6762

COLOR="#000000"

6763

><PRE

6764

CLASS="screen"

6765

> <SAMP

6766

CLASS="prompt"

6767

>cpan></SAMP

6768

>

6769

<B

6770

CLASS="command"

6771

>force install Template</B

6772

>

6773

</PRE

6774

></FONT

6775

></TD

6776

></TR

6777

></TABLE

6778

>

6779

</P

6780

><P

6781

>You may also want to install the other optional modules:</P

6782

><TABLE

6783

BORDER="0"

6784

BGCOLOR="#E0E0E0"

6785

WIDTH="100%"

6786

><TR

6787

><TD

6788

><FONT

6789

COLOR="#000000"

6790

><PRE

6791

CLASS="screen"

6792

> <SAMP

6793

CLASS="prompt"

6794

>cpan></SAMP

6795

>

6796

<B

6797

CLASS="command"

6798

>install GD</B

6799

>

6800

<SAMP

6801

CLASS="prompt"

6802

>cpan></SAMP

6803

>

6804

<B

6805

CLASS="command"

6806

>install Chart::Base</B

6807

>

6808

<SAMP

6809

CLASS="prompt"

6810

>cpan></SAMP

6811

>

6812

<B

6813

CLASS="command"

6814

>install MIME::Parser</B

6815

>

6816

</PRE

6817

></FONT

6818

></TD

6819

></TR

6820

></TABLE

6821

></DIV

6822

></DIV

6823

><DIV

6824

CLASS="section"

6825

><HR><H3

6826

CLASS="section"

6827

><A

6828

NAME="AEN1211"

6829

>4.5.5. HTTP Server</A

6830

></H3

6831

><P

6832

>Ideally, this also needs to be installed as root and

6833

run under a special webserver account. As long as

6834

the web server will allow the running of *.cgi files outside of a

6835

cgi-bin, and a way of denying web access to certain files (such as a

6836

.htaccess file), you should be good in this department.</P

6837

><DIV

6838

CLASS="section"

6839

><HR><H4

6840

CLASS="section"

6841

><A

6842

NAME="AEN1214"

6843

>4.5.5.1. Running Apache as Non-Root</A

6844

></H4

6845

><P

6846

>You can run Apache as a non-root user, but the port will need

6847

to be set to one above 1024. If you type <B

6848

CLASS="command"

6849

>httpd -V</B

6850

>,

6851

you will get a list of the variables that your system copy of httpd

6852

uses. One of those, namely HTTPD_ROOT, tells you where that

6853

installation looks for its config information.</P

6854

><P

6855

>From there, you can copy the config files to your own home

6856

directory to start editing. When you edit those and then use the -d

6857

option to override the HTTPD_ROOT compiled into the web server, you

6858

get control of your own customized web server.</P

6859

><DIV

6860

CLASS="note"

6861

><P

6862

></P

6863

><TABLE

6864

CLASS="note"

6865

WIDTH="100%"

6866

BORDER="0"

6867

><TR

6868

><TD

6869

WIDTH="25"

6870

ALIGN="CENTER"

6871

VALIGN="TOP"

6872

><IMG

6873

SRC="../images/note.gif"

6874

HSPACE="5"

6875

ALT="Note"></TD

6876

><TD

6877

ALIGN="LEFT"

6878

VALIGN="TOP"

6879

><P

6880

>You will need to start the daemons yourself. You can either

6881

ask your system administrator to add them to system startup files, or

6882

add a crontab entry that runs a script to check on these daemons

6883

and restart them if needed.</P

6884

></TD

6885

></TR

6886

></TABLE

6887

></DIV

6888

><DIV

6889

CLASS="warning"

6890

><P

6891

></P

6892

><TABLE

6893

CLASS="warning"

6894

WIDTH="100%"

6895

BORDER="0"

6896

><TR

6897

><TD

6898

WIDTH="25"

6899

ALIGN="CENTER"

6900

VALIGN="TOP"

6901

><IMG

6902

SRC="../images/warning.gif"

6903

HSPACE="5"

6904

ALT="Warning"></TD

6905

><TD

6906

ALIGN="LEFT"

6907

VALIGN="TOP"

6908

><P

6909

>Do NOT run daemons or other services on a server without first

6910

consulting your system administrator! Daemons use up system resources

6911

and running one may be in violation of your terms of service for any

6912

machine on which you are a user!</P

6913

></TD

6914

></TR

6915

></TABLE

6916

></DIV

6917

></DIV

6918

></DIV

6919

><DIV

6920

CLASS="section"

6921

><HR><H3

6922

CLASS="section"

6923

><A

6924

NAME="AEN1223"

6925

>4.5.6. Bugzilla</A

6926

></H3

6927

><P

6928

>Since you probably can't set up a symbolic link to

6929

<TT

6930

CLASS="filename"

6931

>/usr/bonsaitools/bin/perl</TT

6932

> as a non-root user,

6933

you will need to hack the scripts to point to the right Perl:</P

6934

><P

6935

> <TABLE

6936

BORDER="0"

6937

BGCOLOR="#E0E0E0"

6938

WIDTH="100%"

6939

><TR

6940

><TD

6941

><FONT

6942

COLOR="#000000"

6943

><PRE

6944

CLASS="programlisting"

6945

>perl -pi -e

6946

's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm

6947

processmail syncshadowdb</PRE

6948

></FONT

6949

></TD

6950

></TR

6951

></TABLE

6952

>

6953

6954

Change <TT

6955

CLASS="filename"

6956

>/usr/bin/perl</TT

6957

> to match the location

6958

of Perl on your machine. If you had to install Perl as non-root,

6959

this would be the location in your home directory.

6960

</P

6961

><DIV

6962

CLASS="note"

6963

><P

6964

></P

6965

><TABLE

6966

CLASS="note"

6967

WIDTH="100%"

6968

BORDER="0"

6969

><TR

6970

><TD

6971

WIDTH="25"

6972

ALIGN="CENTER"

6973

VALIGN="TOP"

6974

><IMG

6975

SRC="../images/note.gif"

6976

HSPACE="5"

6977

ALT="Note"></TD

6978

><TD

6979

ALIGN="LEFT"

6980

VALIGN="TOP"

6981

><P

6982

>Version 2.17+ of Bugzilla now already has the scripts

6983

pointing to <TT

6984

CLASS="filename"

6985

>/usr/bin/perl</TT

6986

>.</P

6987

></TD

6988

></TR

6989

></TABLE

6990

></DIV

6991

><P

6992

>Of course, the scripts will not work if they don't know the

6993

location of your newly install Perl modules, so you will have to hack

6994

the scripts to look for those, too:</P

6995

><P

6996

> <TABLE

6997

BORDER="0"

6998

BGCOLOR="#E0E0E0"

6999

WIDTH="100%"

7000

><TR

7001

><TD

7002

><FONT

7003

COLOR="#000000"

7004

><PRE

7005

CLASS="programlisting"

7006

>perl -pi -e

7007

's@use strict\;@use strict\; use lib \"/home/foo/perl/lib\"\;@'

7008

*cgi *pl Bug.pm processmail syncshadowdb</PRE

7009

></FONT

7010

></TD

7011

></TR

7012

></TABLE

7013

>

7014

7015

Change <TT

7016

CLASS="filename"

7017

>/home/foo/perl/lib</TT

7018

> to

7019

your personal Perl library directory. You can probably skip this

7020

step if you are using the independant method of Perl module

7021

installation.

7022

</P

7023

><P

7024

>When you run <B

7025

CLASS="command"

7026

>./checksetup.pl</B

7027

> to create

7028

the <TT

7029

CLASS="filename"

7030

>localconfig</TT

7031

> file, it will list the Perl

7032

modules it finds. If one is missing, go back and double-check the

7033

module installation from the CPAN shell, then delete the

7034

<TT

7035

CLASS="filename"

7036

>localconfig</TT

7037

> file and try again.</P

7038

><DIV

7039

CLASS="warning"

7040

><P

7041

></P

7042

><TABLE

7043

CLASS="warning"

7044

WIDTH="100%"

7045

BORDER="0"

7046

><TR

7047

><TD

7048

WIDTH="25"

7049

ALIGN="CENTER"

7050

VALIGN="TOP"

7051

><IMG

7052

SRC="../images/warning.gif"

7053

HSPACE="5"

7054

ALT="Warning"></TD

7055

><TD

7056

ALIGN="LEFT"

7057

VALIGN="TOP"

7058

><P

7059

>The one option in <TT

7060

CLASS="filename"

7061

>localconfig</TT

7062

> you

7063

might have problems with is the web server group. If you can't

7064

successfully browse to the <TT

7065

CLASS="filename"

7066

>index.cgi</TT

7067

> (like

7068

a Forbidden error), you may have to relax your permissions,

7069

and blank out the web server group. Of course, this may pose

7070

as a security risk. Having a properly jailed shell and/or

7071

limited access to shell accounts may lessen the security risk,

7072

but use at your own risk.</P

7073

></TD

7074

></TR

7075

></TABLE

7076

></DIV

7077

></DIV

7078

></DIV

7079

><DIV

7080

CLASS="section"

7081

><HR><H2

6162

7082

CLASS="section"

6163

7083

><A

6164

7084

NAME="troubleshooting"

6165

></A

6166

>4.5. Troubleshooting</H1

7085

>4.6. Troubleshooting</A

7086

></H2

6167

7087

><P

6168

7088

>This section gives solutions to common Bugzilla installation

6169

7089

problems.

6170

7090

</P

6171

7091

><DIV

6172

7092

CLASS="section"

6173

><HR><H2

7093

><HR><H3

6174

7094

CLASS="section"

6175

7095

><A

6176

NAME="AEN1092"

6177

></A

6178

>4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2

7096

NAME="AEN1248"

7097

>4.6.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A

7098

></H3

6179

7099

><P

6180

7100

> Try executing <B

6181

7101

CLASS="command"

6195

7115

></DIV

6196

7116

><DIV

6197

7117

CLASS="section"

6198

><HR><H2

7118

><HR><H3

6199

7119

CLASS="section"

6200

7120

><A

6201

NAME="AEN1097"

6202

></A

6203

>4.5.2. DBD::Sponge::db prepare failed</H2

7121

NAME="AEN1253"

7122

>4.6.2. DBD::Sponge::db prepare failed</A

7123

></H3

6204

7124

><P

6205

7125

> The following error message may appear due to a bug in DBD::mysql

6206

7126

(over which the Bugzilla team have no control):

6281

7201

></DIV

6282

7202

><DIV

6283

7203

CLASS="section"

6284

><HR><H2

7204

><HR><H3

6285

7205

CLASS="section"

6286

7206

><A

6287

7207

NAME="paranoid-security"

6288

></A

6289

>4.5.3. cannot chdir(/var/spool/mqueue)</H2

7208

>4.6.3. cannot chdir(/var/spool/mqueue)</A

7209

></H3

6290

7210

><P

6291

7211

>If you are installing Bugzilla on SuSE Linux, or some other

6292

7212

distributions with

6339

7259

></DIV

6340

7260

><DIV

6341

7261

CLASS="section"

6342

><HR><H2

7262

><HR><H3

6343

7263

CLASS="section"

6344

7264

><A

6345

7265

NAME="trouble-filetemp"

6346

></A

6347

>4.5.4. Your vendor has not defined Fcntl macro O_NOINHERIT</H2

7266

>4.6.4. Your vendor has not defined Fcntl macro O_NOINHERIT</A

7267

></H3

6348

7268

><P

6349

7269

>This is caused by a bug in the version of

6350

7270

<SPAN

6458

7378

>Chapter 5. Administering Bugzilla</H1

6459

7379

><DIV

6460

7380

CLASS="section"

6461

><H1

7381

><H2

6462

7382

CLASS="section"

6463

7383

><A

6464

7384

NAME="parameters"

6465

></A

6466

>5.1. Bugzilla Configuration</H1

7385

>5.1. Bugzilla Configuration</A

7386

></H2

6467

7387

><P

6468

7388

>Bugzilla is configured by changing various parameters, accessed

6469

7389

from the "Edit parameters" link in the page footer. Here are

6529

7449

>off</EM

6530

7450

>

6531

7451

while initially testing your Bugzilla.</P

7452

><P

7453

>For more information see <A

7454

HREF="#groups"

7455

>Section 5.5</A

7456

>.</P

6532

7457

></LI

6533

7458

><LI

6534

7459

><P

6760

7685

></DIV

6761

7686

><DIV

6762

7687

CLASS="section"

6763

><HR><H1

7688

><HR><H2

6764

7689

CLASS="section"

6765

7690

><A

6766

7691

NAME="useradmin"

6767

></A

6768

>5.2. User Administration</H1

7692

>5.2. User Administration</A

7693

></H2

6769

7694

><DIV

6770

7695

CLASS="section"

6771

><H2

7696

><H3

6772

7697

CLASS="section"

6773

7698

><A

6774

7699

NAME="defaultuser"

6775

></A

6776

>5.2.1. Creating the Default User</H2

7700

>5.2.1. Creating the Default User</A

7701

></H3

6777

7702

><P

6778

7703

>When you first run checksetup.pl after installing Bugzilla, it

6779

7704

will prompt you for the administrative username (email address) and

6811

7736

><TBODY

6812

7737

><TR

6813

7738

><TD

6814

> <TT

7739

> <SAMP

6815

7740

CLASS="prompt"

6816

>mysql></TT

7741

>mysql></SAMP

6817

7742

>

6818

7743

<B

6819

7744

CLASS="command"

6823

7748

></TR

6824

7749

><TR

6825

7750

><TD

6826

> <TT

7751

> <SAMP

6827

7752

CLASS="prompt"

6828

>mysql></TT

7753

>mysql></SAMP

6829

7754

>

6830

7755

6831

7756

<B

6832

7757

CLASS="command"

6833

> update profiles set groupset=0x7ffffffffffffff where login_name =

7758

> update profiles set groupset=0x7fffffffffffffff where login_name =

6834

7759

"(user's login name)";

6835

7760

</B

6836

7761

>

6845

7770

><P

6846

7771

>Yes, that is

6847

7772

<EM

6848

>fourteen</EM

7773

>fifteen</EM

6849

7774

>

6850

7775

6851

7776

<SPAN

6862

7787

></DIV

6863

7788

><DIV

6864

7789

CLASS="section"

6865

><HR><H2

7790

><HR><H3

6866

7791

CLASS="section"

6867

7792

><A

6868

7793

NAME="manageusers"

6869

></A

6870

>5.2.2. Managing Other Users</H2

7794

>5.2.2. Managing Other Users</A

7795

></H3

6871

7796

><DIV

6872

7797

CLASS="section"

6873

><H3

7798

><H4

6874

7799

CLASS="section"

6875

7800

><A

6876

7801

NAME="createnewusers"

6877

></A

6878

>5.2.2.1. Creating new users</H3

7802

>5.2.2.1. Creating new users</A

7803

></H4

6879

7804

><P

6880

7805

>Your users can create their own user accounts by clicking the

6881

7806

"New Account" link at the bottom of each page (assuming they

6943

7868

></DIV

6944

7869

><DIV

6945

7870

CLASS="section"

6946

><HR><H3

7871

><HR><H4

6947

7872

CLASS="section"

6948

7873

><A

6949

7874

NAME="modifyusers"

6950

></A

6951

>5.2.2.2. Modifying Users</H3

7875

>5.2.2.2. Modifying Users</A

7876

></H4

6952

7877

><P

6953

7878

>To see a specific user, search for their login name

6954

7879

in the box provided on the "Edit Users" page. To see all users,

7174

8099

></DIV

7175

8100

><DIV

7176

8101

CLASS="section"

7177

><HR><H1

8102

><HR><H2

7178

8103

CLASS="section"

7179

8104

><A

7180

8105

NAME="programadmin"

7181

></A

7182

>5.3. Product, Component, Milestone, and Version Administration</H1

8106

>5.3. Product, Component, Milestone, and Version Administration</A

8107

></H2

7183

8108

><DIV

7184

8109

CLASS="section"

7185

><H2

8110

><H3

7186

8111

CLASS="section"

7187

8112

><A

7188

8113

NAME="products"

7189

></A

7190

>5.3.1. Products</H2

8114

>5.3.1. Products</A

8115

></H3

7191

8116

><P

7192

8117

> <A

7193

8118

HREF="#gloss-product"

7238

8163

></DIV

7239

8164

><DIV

7240

8165

CLASS="section"

7241

><HR><H2

8166

><HR><H3

7242

8167

CLASS="section"

7243

8168

><A

7244

8169

NAME="components"

7245

></A

7246

>5.3.2. Components</H2

8170

>5.3.2. Components</A

8171

></H3

7247

8172

><P

7248

8173

>Components are subsections of a Product. E.g. the computer game

7249

8174

you are designing may have a "UI"

7293

8218

></DIV

7294

8219

><DIV

7295

8220

CLASS="section"

7296

><HR><H2

8221

><HR><H3

7297

8222

CLASS="section"

7298

8223

><A

7299

8224

NAME="versions"

7300

></A

7301

>5.3.3. Versions</H2

8225

>5.3.3. Versions</A

8226

></H3

7302

8227

><P

7303

8228

>Versions are the revisions of the product, such as "Flinders

7304

8229

3.1", "Flinders 95", and "Flinders 2000". Version is not a multi-select

7329

8254

></DIV

7330

8255

><DIV

7331

8256

CLASS="section"

7332

><HR><H2

8257

><HR><H3

7333

8258

CLASS="section"

7334

8259

><A

7335

8260

NAME="milestones"

7336

></A

7337

>5.3.4. Milestones</H2

8261

>5.3.4. Milestones</A

8262

></H3

7338

8263

><P

7339

8264

>Milestones are "targets" that you plan to get a bug fixed by. For

7340

8265

example, you have a bug that you plan to fix for your 3.0 release, it

7432

8357

></DIV

7433

8358

><DIV

7434

8359

CLASS="section"

7435

><HR><H1

8360

><HR><H2

7436

8361

CLASS="section"

7437

8362

><A

7438

8363

NAME="voting"

7439

></A

7440

>5.4. Voting</H1

8364

>5.4. Voting</A

8365

></H2

7441

8366

><P

7442

8367

>Voting allows users to be given a pot of votes which they can allocate

7443

8368

to bugs, to indicate that they'd like them fixed.

7494

8419

></DIV

7495

8420

><DIV

7496

8421

CLASS="section"

7497

><HR><H1

8422

><HR><H2

7498

8423

CLASS="section"

7499

8424

><A

7500

8425

NAME="groups"

7501

></A

7502

>5.5. Groups and Group Security</H1

8426

>5.5. Groups and Group Security</A

8427

></H2

7503

8428

><P

7504

8429

>Groups allow the administrator

7505

8430

to isolate bugs or products that should only be seen by certain people.

7637

8562

></DIV

7638

8563

><DIV

7639

8564

CLASS="section"

7640

><HR><H1

8565

><HR><H2

7641

8566

CLASS="section"

7642

8567

><A

7643

8568

NAME="security"

7644

></A

7645

>5.6. Bugzilla Security</H1

8569

>5.6. Bugzilla Security</A

8570

></H2

7646

8571

><DIV

7647

8572

CLASS="warning"

7648

8573

><P

7697

8622

>These instructions must, of necessity, be somewhat vague since

7698

8623

Bugzilla runs on so many different platforms. If you have refinements

7699

8624

of these directions, please submit a bug to <A

7700

HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"

8625

HREF="http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&component=Documentation"

7701

8626

TARGET="_top"

7702

8627

>Bugzilla</A

7703

8628

>.

7738

8663

></DIV

7739

8664

><DIV

7740

8665

CLASS="section"

7741

><HR><H2

8666

><HR><H3

7742

8667

CLASS="section"

7743

8668

><A

7744

8669

NAME="security-networking"

7745

></A

7746

>5.6.1. TCP/IP Ports</H2

8670

>5.6.1. TCP/IP Ports</A

8671

></H3

7747

8672

><P

7748

8673

>TCP/IP defines 65,000 some ports for trafic. Of those, Bugzilla

7749

8674

only needs 1... 2 if you need to use features that require e-mail such

7756

8681

></DIV

7757

8682

><DIV

7758

8683

CLASS="section"

7759

><HR><H2

8684

><HR><H3

7760

8685

CLASS="section"

7761

8686

><A

7762

8687

NAME="security-mysql"

7763

></A

7764

>5.6.2. MySQL</H2

8688

>5.6.2. MySQL</A

8689

></H3

7765

8690

><P

7766

8691

>MySQL ships by default with many settings that should be changed.

7767

8692

By defaults it allows anybody to connect from localhost without a

7811

8736

COLOR="#000000"

7812

8737

><PRE

7813

8738

CLASS="programlisting"

7814

><TT

8739

><SAMP

7815

8740

CLASS="prompt"

7816

>bash$</TT

8741

>bash$</SAMP

7817

8742

> mysql mysql

7818

<TT

8743

<SAMP

7819

8744

CLASS="prompt"

7820

>mysql></TT

8745

>mysql></SAMP

7821

8746

> DELETE FROM user WHERE user = '';

7822

<TT

8747

<SAMP

7823

8748

CLASS="prompt"

7824

>mysql></TT

7825

> UPDATE user SET password = password('<TT

8749

>mysql></SAMP

8750

> UPDATE user SET password = password('<VAR

7826

8751

CLASS="replaceable"

7827

><I

7828

>new_password</I

7829

></TT

8752

>new_password</VAR

7830

8753

>') WHERE user = 'root';

7831

<TT

8754

<SAMP

7832

8755

CLASS="prompt"

7833

>mysql></TT

8756

>mysql></SAMP

7834

8757

> FLUSH PRIVILEGES;

7835

8758

</PRE

7836

8759

></FONT

7843

8766

CLASS="command"

7844

8767

>mysql -u root -p</B

7845

8768

> and enter

7846

<TT

8769

<VAR

7847

8770

CLASS="replaceable"

7848

><I

7849

>new_password</I

7850

></TT

8771

>new_password</VAR

7851

8772

> when prompted when using the

7852

8773

mysql client.

7853

8774

</P

7858

8779

should consider disabling networking from within MySQL by adding

7859

8780

the following to your <TT

7860

8781

CLASS="filename"

7861

>/etc/my.conf</TT

8782

>/etc/my.cnf</TT

7862

8783

>:

7863

8784

</P

7864

8785

><TABLE

7891

8812

></DIV

7892

8813

><DIV

7893

8814

CLASS="section"

7894

><HR><H2

8815

><HR><H3

7895

8816

CLASS="section"

7896

8817

><A

7897

8818

NAME="security-daemon"

7898

></A

7899

>5.6.3. Daemon Accounts</H2

8819

>5.6.3. Daemon Accounts</A

8820

></H3

7900

8821

><P

7901

8822

>Many daemons, such as Apache's httpd and MySQL's mysqld default to

7902

8823

running as either <SPAN

7943

8864

ALIGN="LEFT"

7944

8865

VALIGN="TOP"

7945

8866

><P

7946

>You will need to set the <TT

8867

>You will need to set the <VAR

7947

8868

CLASS="varname"

7948

>webservergroup</TT

8869

>webservergroup</VAR

7949

8870

> to

7950

8871

the group you created for your webserver to run as in

7951

8872

<TT

7966

8887

></DIV

7967

8888

><DIV

7968

8889

CLASS="section"

7969

><HR><H2

8890

><HR><H3

7970

8891

CLASS="section"

7971

8892

><A

7972

8893

NAME="security-access"

7973

></A

7974

>5.6.4. Web Server Access Controls</H2

8894

>5.6.4. Web Server Access Controls</A

8895

></H3

7975

8896

><P

7976

8897

>There are many files that are placed in the Bugzilla directory

7977

8898

area that should not be accessable from the web. Because of the way

8257

9178

></DIV

8258

9179

><DIV

8259

9180

CLASS="section"

8260

><HR><H1

9181

><HR><H2

8261

9182

CLASS="section"

8262

9183

><A

8263

9184

NAME="cust-templates"

8264

></A

8265

>5.7. Template Customisation</H1

9185

>5.7. Template Customisation</A

9186

></H2

8266

9187

><P

8267

9188

> One of the large changes for 2.16 was the templatisation of the

8268

9189

entire user-facing UI, using the

8283

9204

</P

8284

9205

><DIV

8285

9206

CLASS="section"

8286

><HR><H2

9207

><HR><H3

8287

9208

CLASS="section"

8288

9209

><A

8289

NAME="AEN1534"

8290

></A

8291

>5.7.1. What to Edit</H2

9210

NAME="AEN1692"

9211

>5.7.1. What to Edit</A

9212

></H3

8292

9213

><P

8293

9214

> There are two different ways of editing of Bugzilla's templates,

8294

9215

and which you use depends mainly on how you upgrade Bugzilla. The

8433

9354

></DIV

8434

9355

><DIV

8435

9356

CLASS="section"

8436

><HR><H2

9357

><HR><H3

8437

9358

CLASS="section"

8438

9359

><A

8439

NAME="AEN1557"

8440

></A

8441

>5.7.2. How To Edit Templates</H2

9360

NAME="AEN1715"

9361

>5.7.2. How To Edit Templates</A

9362

></H3

8442

9363

><P

8443

9364

> The syntax of the Template Toolkit language is beyond the scope of

8444

9365

this guide. It's reasonably easy to pick up by looking at the current

8515

9436

></DIV

8516

9437

><DIV

8517

9438

CLASS="section"

8518

><HR><H2

9439

><HR><H3

8519

9440

CLASS="section"

8520

9441

><A

8521

NAME="AEN1567"

8522

></A

8523

>5.7.3. Template Formats</H2

9442

NAME="AEN1725"

9443

>5.7.3. Template Formats</A

9444

></H3

8524

9445

><P

8525

9446

> Some CGIs have the ability to use more than one template. For

8526

9447

example, buglist.cgi can output bug lists as RDF or two

8577

9498

></DIV

8578

9499

><DIV

8579

9500

CLASS="section"

8580

><HR><H2

9501

><HR><H3

8581

9502

CLASS="section"

8582

9503

><A

8583

NAME="AEN1580"

8584

></A

8585

>5.7.4. Particular Templates</H2

9504

NAME="AEN1738"

9505

>5.7.4. Particular Templates</A

9506

></H3

8586

9507

><P

8587

9508

> There are a few templates you may be particularly interested in

8588

9509

customising for your installation.

8752

9673

></DIV

8753

9674

><DIV

8754

9675

CLASS="section"

8755

><HR><H1

9676

><HR><H2

8756

9677

CLASS="section"

8757

9678

><A

8758

9679

NAME="upgrading"

8759

></A

8760

>5.8. Upgrading to New Releases</H1

9680

>5.8. Upgrading to New Releases</A

9681

></H2

8761

9682

><P

8762

9683

>Upgrading Bugzilla is something we all want to do from time to time,

8763

9684

be it to get new features or pick up the latest security fix. How easy

8811

9732

><P

8812

9733

>Revisions are normally released to fix security vulnerabilities

8813

9734

and are distinguished by an increase in the third number. For example,

8814

when 2.16.2 was released, it was a revision to 2.16.1.

9735

when 2.16.6 was released, it was a revision to 2.16.5.

8815

9736

</P

8816

9737

><P

8817

9738

>Point releases are normally released when the Bugzilla team feels

8820

9741

stabilization period and release candidates, however the use of

8821

9742

development versions or release candidates is beyond the scope of this

8822

9743

document. Point releases can be distinguished by an increase in the

8823

second number, or minor version. For example, 2.16.2 is a newer point

8824

release than 2.14.5.

9744

second number, or minor version. For example, 2.18.0 is a newer point

9745

release than 2.16.5.

8825

9746

</P

8826

9747

><P

8827

9748

>The examples in this section are written as if you were updating

8828

to version 2.16.2. The procedures are the same regardless if you are

9749

to version 2.16.6. The procedures are the same regardless if you are

8829

9750

updating to a new point release or a new revision. However, the chance

8830

9751

of running into trouble increases when upgrading to a new point release,

8831

9752

escpecially if you've made local changes.

8909

9830

>

8910

9831

bash$ <B

8911

9832

CLASS="command"

8912

>cvs -q update -r BUGZILLA-2_16_2 -dP</B

9833

>cvs -q update -r BUGZILLA-2_16_6 -dP</B

8913

9834

>

8914

9835

P checksetup.pl

8915

9836

P collectstats.pl

8947

9868

CLASS="command"

8948

9869

>cvs update</B

8949

9870

>

8950

begins with a <TT

9871

begins with a <SAMP

8951

9872

CLASS="computeroutput"

8952

>C</TT

9873

>C</SAMP

8953

9874

> that represents a

8954

9875

file with local changes that CVS was unable to properly merge. You

8955

9876

need to resolve these conflicts manually before Bugzilla (or at

9025

9946

>

9026

9947

bash$ <B

9027

9948

CLASS="command"

9028

>wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz</B

9949

>wget ftp://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-2.16.6.tar.gz</B

9029

9950

>

9030

9951

<EM

9031

9952

>Output omitted</EM

9032

9953

>

9033

9954

bash$ <B

9034

9955

CLASS="command"

9035

>tar xzvf bugzilla-2.16.2.tar.gz</B

9956

>tar xzvf bugzilla-2.16.6.tar.gz</B

9036

9957

>

9037

bugzilla-2.16.2/

9038

bugzilla-2.16.2/.cvsignore

9039

bugzilla-2.16.2/1x1.gif

9958

bugzilla-2.16.6/

9959

bugzilla-2.16.6/.cvsignore

9960

bugzilla-2.16.6/1x1.gif

9040

9961

<EM

9041

9962

>Output truncated</EM

9042

9963

>

9043

9964

bash$ <B

9044

9965

CLASS="command"

9045

>cd bugzilla-2.16.2</B

9966

>cd bugzilla-2.16.6</B

9046

9967

>

9047

9968

bash$ <B

9048

9969

CLASS="command"

9062

9983

>

9063

9984

bash$ <B

9064

9985

CLASS="command"

9065

>mv bugzilla-2.16.2 bugzilla</B

9986

>mv bugzilla-2.16.6 bugzilla</B

9066

9987

>

9067

9988

bash$ <B

9068

9989

CLASS="command"

9188

10109

>

9189

10110

bash$ <B

9190

10111

CLASS="command"

9191

>wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz</B

10112

>wget ftp://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-2.16.5-to-2.16.6.diff.gz</B

9192

10113

>

9193

10114

<EM

9194

10115

>Output omitted</EM

9195

10116

>

9196

10117

bash$ <B

9197

10118

CLASS="command"

9198

>gunzip bugzilla-2.16.1-to-2.16.2.diff.gz</B

10119

>gunzip bugzilla-2.16.5-to-2.16.6.diff.gz</B

9199

10120

>

9200

10121

bash$ <B

9201

10122

CLASS="command"

9202

>patch -p1 < bugzilla-2.16.1-to-2.16.2.diff</B

10123

>patch -p1 < bugzilla-2.16.5-to-2.16.6.diff</B

9203

10124

>

9204

10125

patching file checksetup.pl

9205

10126

patching file collectstats.pl

9252

10173

></DIV

9253

10174

><DIV

9254

10175

CLASS="section"

9255

><HR><H1

10176

><HR><H2

9256

10177

CLASS="section"

9257

10178

><A

9258

10179

NAME="integration"

9259

></A

9260

>5.9. Integrating Bugzilla with Third-Party Tools</H1

10180

>5.9. Integrating Bugzilla with Third-Party Tools</A

10181

></H2

9261

10182

><DIV

9262

10183

CLASS="section"

9263

><H2

10184

><H3

9264

10185

CLASS="section"

9265

10186

><A

9266

10187

NAME="bonsai"

9267

></A

9268

>5.9.1. Bonsai</H2

10188

>5.9.1. Bonsai</A

10189

></H3

9269

10190

><P

9270

10191

>Bonsai is a web-based tool for managing

9271

10192

<A

9286

10207

></DIV

9287

10208

><DIV

9288

10209

CLASS="section"

9289

><HR><H2

10210

><HR><H3

9290

10211

CLASS="section"

9291

10212

><A

9292

10213

NAME="cvs"

9293

></A

9294

>5.9.2. CVS</H2

10214

>5.9.2. CVS</A

10215

></H3

9295

10216

><P

9296

10217

>CVS integration is best accomplished, at this point, using the

9297

10218

Bugzilla Email Gateway.</P

9320

10241

> http://homepages.kcbbs.gen.nz/~tonyg/</A

9321

10242

>.

9322

10243

</P

10244

><P

10245

>Another system capable of CVS integration with Bugzilla is

10246

Scmbug. This system provides generic integration of Source code

10247

Configuration Management with Bugtracking. Check it out at: <A

10248

HREF="http://freshmeat.net/projects/scmbug/"

10249

TARGET="_top"

10250

>http://freshmeat.net/projects/scmbug/</A

10251

>.

10252

</P

9323

10253

></DIV

9324

10254

><DIV

9325

10255

CLASS="section"

9326

><HR><H2

10256

><HR><H3

9327

10257

CLASS="section"

9328

10258

><A

9329

10259

NAME="scm"

9330

></A

9331

>5.9.3. Perforce SCM</H2

10260

>5.9.3. Perforce SCM</A

10261

></H3

9332

10262

><P

9333

10263

>You can find the project page for Bugzilla and Teamtrack Perforce

9334

10264

integration (p4dti) at:

9363

10293

></DIV

9364

10294

><DIV

9365

10295

CLASS="section"

9366

><HR><H2

10296

><HR><H3

10297

CLASS="section"

10298

><A

10299

NAME="svn"

10300

>5.9.4. Subversion</A

10301

></H3

10302

><P

10303

>Subversion is a free/open-source version control system,

10304

designed to overcome various limitations of CVS. Integration of

10305

Subversion with Bugzilla is possible using Scmbug, a system

10306

providing generic integration of Source Code Configuration

10307

Management with Bugtracking. Scmbug is available at <A

10308

HREF="http://freshmeat.net/projects/scmbug/"

10309

TARGET="_top"

10310

>http://freshmeat.net/projects/scmbug/</A

10311

>.</P

10312

></DIV

10313

><DIV

10314

CLASS="section"

10315

><HR><H3

9367

10316

CLASS="section"

9368

10317

><A

9369

10318

NAME="tinderbox"

9370

></A

9371

>5.9.4. Tinderbox/Tinderbox2</H2

10319

>5.9.5. Tinderbox/Tinderbox2</A

10320

></H3

9372

10321

><P

9373

10322

>We need Tinderbox integration information.</P

9374

10323

></DIV

9595

10544

></DT

9596

10545

><DT

9597

10546

>A.2.18. <A

10547

HREF="#faq-phb-cvsupdate"

10548

> How can I update the code and the database using CVS?

10549

</A

10550

></DT

10551

><DT

10552

>A.2.19. <A

9598

10553

HREF="#faq-phb-maintenance"

9599

10554

> What type of human resources are needed to be on staff to install and

9600

10555

maintain Bugzilla? Specifically, what type of skills does the person need to

9604

10559

</A

9605

10560

></DT

9606

10561

><DT

9607

>A.2.19. <A

10562

>A.2.20. <A

9608

10563

HREF="#faq-phb-installtime"

9609

10564

> What time frame are we looking at if we decide to hire people to install

9610

10565

and maintain the Bugzilla? Is this something that takes hours or weeks to

9614

10569

</A

9615

10570

></DT

9616

10571

><DT

9617

>A.2.20. <A

10572

>A.2.21. <A

9618

10573

HREF="#faq-phb-cost"

9619

10574

> Is there any licensing fee or other fees for using Bugzilla? Any

9620

10575

out-of-pocket cost other than the bodies needed as identified above?

9621

10576

</A

9622

10577

></DT

10578

><DT

10579

>A.2.22. <A

10580

HREF="#faq-phb-reloginEveryone"

10581

> Why do users have to log in every time they access a page? This

10582

affects everyone who accesses my Bugzilla. (If this only affects

10583

some of your users, see the next FAQ item.)

10584

</A

10585

></DT

10586

><DT

10587

>A.2.23. <A

10588

HREF="#faq-phb-reloginSome"

10589

> Why do users have to log in every time they access a page? This

10590

only seems to affect some of my Bugzilla's users, others stay

10591

logged in.

10592

</A

10593

></DT

9623

10594

></DL

9624

10595

></DD

9625

10596

><DT

10973

11944

CLASS="question"

10974

11945

><P

10975

11946

><A

11947

NAME="faq-phb-cvsupdate"

11948

></A

11949

><B

11950

>A.2.18. </B

11951

>

11952

How can I update the code and the database using CVS?

11953

</P

11954

></DIV

11955

><DIV

11956

CLASS="answer"

11957

><P

11958

><B

11959

> </B

11960

>

11961

<P

11962

></P

11963

><OL

11964

TYPE="1"

11965

><LI

11966

><P

11967

> Make a backup of both your Bugzilla directory and the

11968

database. For the Bugzilla directory this is as easy as

11969

doing <B

11970

CLASS="command"

11971

>cp -rp bugzilla bugzilla.bak</B

11972

>.

11973

For the database, there's a number of options - see the

11974

MySQL docs and pick the one that fits you best (the easiest

11975

is to just make a physical copy of the database on the disk,

11976

but you have to have the database server shut down to do

11977

that without risking dataloss).

11978

</P

11979

></LI

11980

><LI

11981

><P

11982

> Make the Bugzilla directory your current directory.

11983

</P

11984

></LI

11985

><LI

11986

><P

11987

> Use <B

11988

CLASS="command"

11989

>cvs -q update -AdP</B

11990

> if you want to

11991

update to the tip or

11992

<B

11993

CLASS="command"

11994

>cvs -q update -dP -rTAGNAME</B

11995

>

11996

if you want a specific version (in that case you'll have to

11997

replace TAGNAME with a CVS tag name such as BUGZILLA-2_16_5).

11998

</P

11999

><P

12000

> If you've made no local changes, this should be very clean.

12001

If you have made local changes, then watch the cvs output

12002

for C results. If you get any lines that start with a C

12003

it means there were conflicts between your local changes

12004

and what's in CVS. You'll need to fix those manually before

12005

continuing.

12006

</P

12007

></LI

12008

><LI

12009

><P

12010

> After resolving any conflicts that the cvs update operation

12011

generated, running <B

12012

CLASS="command"

12013

>./checksetup.pl</B

12014

> will

12015

take care of updating the database for you as well as any

12016

other changes required for the new version to operate.

12017

</P

12018

><DIV

12019

CLASS="warning"

12020

><P

12021

></P

12022

><TABLE

12023

CLASS="warning"

12024

WIDTH="100%"

12025

BORDER="0"

12026

><TR

12027

><TD

12028

WIDTH="25"

12029

ALIGN="CENTER"

12030

VALIGN="TOP"

12031

><IMG

12032

SRC="../images/warning.gif"

12033

HSPACE="5"

12034

ALT="Warning"></TD

12035

><TD

12036

ALIGN="LEFT"

12037

VALIGN="TOP"

12038

><P

12039

> Once you run checksetup.pl, the only way to go back is

12040

to restore the database backups. You can't "downgrade"

12041

the system cleanly under most circumstances.

12042

</P

12043

></TD

12044

></TR

12045

></TABLE

12046

></DIV

12047

></LI

12048

></OL

12049

>

12050

</P

12051

></DIV

12052

></DIV

12053

><DIV

12054

CLASS="qandaentry"

12055

><DIV

12056

CLASS="question"

12057

><P

12058

><A

10976

12059

NAME="faq-phb-maintenance"

10977

12060

></A

10978

12061

><B

10979

>A.2.18. </B

12062

>A.2.19. </B

10980

12063

>

10981

12064

What type of human resources are needed to be on staff to install and

10982

12065

maintain Bugzilla? Specifically, what type of skills does the person need to

11011

12094

NAME="faq-phb-installtime"

11012

12095

></A

11013

12096

><B

11014

>A.2.19. </B

12097

>A.2.20. </B

11015

12098

>

11016

12099

What time frame are we looking at if we decide to hire people to install

11017

12100

and maintain the Bugzilla? Is this something that takes hours or weeks to

11044

12127

NAME="faq-phb-cost"

11045

12128

></A

11046

12129

><B

11047

>A.2.20. </B

12130

>A.2.21. </B

11048

12131

>

11049

12132

Is there any licensing fee or other fees for using Bugzilla? Any

11050

12133

out-of-pocket cost other than the bodies needed as identified above?

11061

12144

</P

11062

12145

></DIV

11063

12146

></DIV

12147

><DIV

12148

CLASS="qandaentry"

12149

><DIV

12150

CLASS="question"

12151

><P

12152

><A

12153

NAME="faq-phb-reloginEveryone"

12154

></A

12155

><B

12156

>A.2.22. </B

12157

>

12158

Why do users have to log in every time they access a page? This

12159

affects everyone who accesses my Bugzilla. (If this only affects

12160

some of your users, see the next FAQ item.)

12161

</P

12162

></DIV

12163

><DIV

12164

CLASS="answer"

12165

><P

12166

><B

12167

> </B

12168

>

12169

The most-likely cause is that the "cookiepath" parameter is not set

12170

correctly in the Bugzilla configuration. You can change this (if

12171

you're a Bugzilla administrator) from the editparams.cgi page

12172

via the web.

12173

</P

12174

><P

12175

> The value of the cookiepath parameter should be the actual directory

12176

containing your Bugzilla installation, <EM

12177

>as seen by the

12178

end-user's web browser</EM

12179

>. Leading and trailing slashes are

12180

mandatory. You can also set the cookiepath to any directory which

12181

is a parent of the Bugzilla directory (such as '/', the root

12182

directory). But you can't put something that isn't at least

12183

a partial match or it won't work. What you're actually doing

12184

is restricting the end-user's browser to sending the cookies

12185

back only to that directory.

12186

</P

12187

><P

12188

> How do you know if you want your specific Bugzilla directory or the

12189

whole site?

12190

</P

12191

><P

12192

> If you have only one Bugzilla running on the server, and you

12193

don't mind having other applications on the same server with it

12194

being able to see the cookies (you might be doing this on purpose

12195

if you have other things on your site that share authentication with

12196

Bugzilla), then you'll want to have the cookiepath set to "/", or to

12197

a sufficiently-high enough directory that all of the involved apps

12198

can see the cookies.

12199

</P

12200

><P

12201

> Examples:

12202

12203

<A

12204

NAME="AEN2132"

12205

></A

12206

><BLOCKQUOTE

12207

CLASS="BLOCKQUOTE"

12208

><P

12209

CLASS="literallayout"

12210

><br>

12211

        urlbase is <A

12212

HREF="http://bugzilla.mozilla.org/"

12213

TARGET="_top"

12214

>http://bugzilla.mozilla.org/</A

12215

><br>

12216

        cookiepath is /<br>

12217

<br>

12218

        urlbase is <A

12219

HREF="http://tools.mysite.tld/bugzilla/"

12220

TARGET="_top"

12221

>http://tools.mysite.tld/bugzilla/</A

12222

><br>

12223

                but you have http://tools.mysite.tld/someotherapp/ which shares<br>

12224

                authentication with your Bugzilla<br>

12225

        cookiepath is /<br>

12226

              </P

12227

></BLOCKQUOTE

12228

>

12229

</P

12230

><P

12231

> On the other hand, if you have more than one Bugzilla

12232

running on the server (some people do - we do on landfill)

12233

then you need to have the cookiepath restricted enough

12234

so that the different Bugzillas don't

12235

confuse their cookies with one another.

12236

</P

12237

><P

12238

> Examples:

12239

12240

<A

12241

NAME="AEN2138"

12242

></A

12243

><BLOCKQUOTE

12244

CLASS="BLOCKQUOTE"

12245

><P

12246

CLASS="literallayout"

12247

><br>

12248

        urlbase is <A

12249

HREF="http://landfill.bugzilla.org/bugzilla-tip/"

12250

TARGET="_top"

12251

>http://landfill.bugzilla.org/bugzilla-tip/</A

12252

><br>

12253

        cookiepath is /bugzilla-tip/<br>

12254

<br>

12255

        urlbase is <A

12256

HREF="http://landfill.bugzilla.org/bugzilla-2.16-branch/"

12257

TARGET="_top"

12258

>http://landfill.bugzilla.org/bugzilla-2.16-branch/</A

12259

><br>

12260

        cookiepath is /bugzilla-2.16-branch/<br>

12261

              </P

12262

></BLOCKQUOTE

12263

>

12264

</P

12265

><P

12266

> If you had cookiepath set to / at any point in the past and

12267

need to set it to something more restrictive (i.e. /bugzilla/),

12268

you can safely do this without requiring users to delete

12269

their Bugzilla-related cookies in their browser (this is

12270

true starting with Bugzilla 2.17.7 and Bugzilla 2.16.5).

12271

</P

12272

></DIV

12273

></DIV

12274

><DIV

12275

CLASS="qandaentry"

12276

><DIV

12277

CLASS="question"

12278

><P

12279

><A

12280

NAME="faq-phb-reloginSome"

12281

></A

12282

><B

12283

>A.2.23. </B

12284

>

12285

Why do users have to log in every time they access a page? This

12286

only seems to affect some of my Bugzilla's users, others stay

12287

logged in.

12288

</P

12289

></DIV

12290

><DIV

12291

CLASS="answer"

12292

><P

12293

><B

12294

> </B

12295

>

12296

First, make sure cookies are enabled in the user's browser.

12297

</P

12298

><P

12299

> If that doesn't fix the problem, it may be that

12300

the user's ISP implements a rotating proxy server. This causes

12301

the user's effective IP address (the address which the Bugzilla server

12302

perceives him coming from) to change periodically. Since

12303

Bugzilla cookies are tied to a specific IP address, each time

12304

the effective address changes, the user will have to log in again.

12305

</P

12306

><P

12307

> In newer versions of Bugzilla (2.17.1 and later) there is a

12308

parameter called "loginnetmask", which you can use to set the

12309

number of bits of the user's IP address to require to be matched

12310

when authenticating the cookies. If you set this to something less

12311

than 32, then the user will be given a checkbox for "Restrict this

12312

login to my IP address" on the login screen, which defaults to

12313

checked. If they leave the box checked, Bugzilla will behave the

12314

same as it did before, requiring an exact match on their IP address

12315

to remain logged in. If they uncheck the box, then only the left

12316

side of their IP address (up to the number of bits you specified in

12317

the parameter) has to match to remain logged in.

12318

</P

12319

></DIV

12320

></DIV

11064

12321

></DIV

11065

12322

><DIV

11066

12323

CLASS="qandadiv"

11274

12531

You can call bug_email.pl directly from your aliases file, with

11275

12532

an entry like this:

11276

12533

<A

11277

NAME="AEN1979"

12534

NAME="AEN2192"

11278

12535

></A

11279

12536

><BLOCKQUOTE

11280

12537

CLASS="BLOCKQUOTE"

11692

12949

><P

11693

12950

> Microsoft has some advice on this matter, as well:

11694

12951

<A

11695

NAME="AEN2055"

12952

NAME="AEN2268"

11696

12953

></A

11697

12954

><BLOCKQUOTE

11698

12955

CLASS="BLOCKQUOTE"

11759

13016

></LI

11760

13017

><LI

11761

13018

><P

11762

> <TT

13019

> <SAMP

11763

13020

CLASS="prompt"

11764

>PPM></TT

13021

>PPM></SAMP

11765

13022

> <B

11766

13023

CLASS="command"

11767

13024

>install DBI DBD-mysql GD</B

12013

13270

> </B

12014

13271

>

12015

13272

Try <A

12016

HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Bugzilla"

13273

HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Bugzilla"

12017

13274

TARGET="_top"

12018

13275

> this link</A

12019

13276

> to view current bugs or requests for

12022

13279

><P

12023

13280

> You can view bugs marked for 2.18 release

12024

13281

<A

12025

HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.18"

13282

HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&target_milestone=Bugzilla+2.18"

12026

13283

TARGET="_top"

12027

13284

>here</A

12028

13285

>.

12186

13443

></DIV

12187

13444

><DIV

12188

13445

CLASS="section"

12189

><HR><H1

13446

><HR><H2

12190

13447

CLASS="section"

12191

13448

><A

12192

13449

NAME="dbschema"

12193

></A

12194

>B.1. Database Schema Chart</H1

13450

>B.1. Database Schema Chart</A

13451

></H2

12195

13452

><P

12196

13453

> <DIV

12197

13454

CLASS="mediaobject"

12209

13466

></DIV

12210

13467

><DIV

12211

13468

CLASS="section"

12212

><HR><H1

13469

><HR><H2

12213

13470

CLASS="section"

12214

13471

><A

12215

13472

NAME="dbdoc"

12216

></A

12217

>B.2. MySQL Bugzilla Database Introduction</H1

13473

>B.2. MySQL Bugzilla Database Introduction</A

13474

></H2

12218

13475

><P

12219

13476

>This information comes straight from my life. I was forced to learn

12220

13477

how Bugzilla organizes database because of nitpicky requests from users

12271

13528

tinyint definitions. The Adventure Awaits You!</P

12272

13529

><DIV

12273

13530

CLASS="section"

12274

><HR><H2

13531

><HR><H3

12275

13532

CLASS="section"

12276

13533

><A

12277

NAME="AEN2175"

12278

></A

12279

>B.2.1. Bugzilla Database Basics</H2

13534

NAME="AEN2388"

13535

>B.2.1. Bugzilla Database Basics</A

13536

></H3

12280

13537

><P

12281

13538

>If you were like me, at this point you're totally clueless about

12282

13539

the internals of MySQL, and if it weren't for this executive order from

12312

13569

><P

12313

13570

>To connect to your database:</P

12314

13571

><P

12315

> <TT

13572

> <SAMP

12316

13573

CLASS="prompt"

12317

>bash#</TT

13574

>bash#</SAMP

12318

13575

>

12319

13576

12320

13577

<B

12322

13579

>mysql</B

12323

13580

>

12324

13581

12325

<TT

13582

<VAR

12326

13583

CLASS="parameter"

12327

><I

12328

>-u root</I

12329

></TT

13584

>-u root</VAR

12330

13585

>

12331

13586

</P

12332

13587

><P

12351

13606

><P

12352

13607

>You should now be at a prompt that looks like this:</P

12353

13608

><P

12354

> <TT

13609

> <SAMP

12355

13610

CLASS="prompt"

12356

>mysql></TT

13611

>mysql></SAMP

12357

13612

>

12358

13613

</P

12359

13614

><P

12371

13626

12372

13627

file for your Bugzilla database, type:</P

12373

13628

><P

12374

> <TT

13629

> <SAMP

12375

13630

CLASS="prompt"

12376

>mysql</TT

13631

>mysql</SAMP

12377

13632

>

12378

13633

12379

13634

<B

12387

13642

</P

12388

13643

><DIV

12389

13644

CLASS="section"

12390

><HR><H3

13645

><HR><H4

12391

13646

CLASS="section"

12392

13647

><A

12393

NAME="AEN2202"

12394

></A

12395

>B.2.1.1. Bugzilla Database Tables</H3

13648

NAME="AEN2415"

13649

>B.2.1.1. Bugzilla Database Tables</A

13650

></H4

12396

13651

><P

12397

13652

>Imagine your MySQL database as a series of spreadsheets, and

12398

13653

you won't be too far off. If you use this command:</P

12399

13654

><P

12400

> <TT

13655

> <SAMP

12401

13656

CLASS="prompt"

12402

>mysql></TT

13657

>mysql></SAMP

12403

13658

>

12404

13659

<B

12405

13660

CLASS="command"

12640

13895

some of the niftiest tricks here in this section.</P

12641

13896

><DIV

12642

13897

CLASS="section"

12643

><HR><H1

13898

><HR><H2

12644

13899

CLASS="section"

12645

13900

><A

12646

13901

NAME="rewrite"

12647

></A

12648

13902

>C.1. Apache

12649

13903

<TT

12650

13904

CLASS="filename"

12651

13905

>mod_rewrite</TT

12652

13906

>

12653

13907

12654

magic</H1

13908

magic</A

13909

></H2

12655

13910

><P

12656

13911

>Apache's

12657

13912

<TT

12668

13923

><LI

12669

13924

><P

12670

13925

>Make it so if someone types

12671

<TT

13926

<SAMP

12672

13927

CLASS="computeroutput"

12673

>http://www.foo.com/12345</TT

13928

>http://www.foo.com/12345</SAMP

12674

13929

>

12675

13930

12676

13931

, Bugzilla spits back http://www.foo.com/show_bug.cgi?id=12345. Try

12711

13966

></DIV

12712

13967

><DIV

12713

13968

CLASS="section"

12714

><HR><H1

13969

><HR><H2

12715

13970

CLASS="section"

12716

13971

><A

12717

13972

NAME="cmdline"

12718

></A

12719

>C.2. Command-line Bugzilla Queries</H1

13973

>C.2. Command-line Bugzilla Queries</A

13974

></H2

12720

13975

><P

12721

13976

>There are a suite of Unix utilities for querying Bugzilla from the

12722

13977

command line. They live in the

12812

14067

</P

12813

14068

><DIV

12814

14069

CLASS="section"

12815

><HR><H1

14070

><HR><H2

12816

14071

CLASS="section"

12817

14072

><A

12818

14073

NAME="variant-redhat"

12819

></A

12820

>D.1. Red Hat Bugzilla</H1

14074

>D.1. Red Hat Bugzilla</A

14075

></H2

12821

14076

><P

12822

14077

>Red Hat's old fork of Bugzilla which was based on version 2.8 is now

12823

14078

obsolete. The newest version in use is based on version 2.17.1 and is in

12847

14102

></DIV

12848

14103

><DIV

12849

14104

CLASS="section"

12850

><HR><H1

14105

><HR><H2

12851

14106

CLASS="section"

12852

14107

><A

12853

14108

NAME="variant-fenris"

12854

></A

12855

>D.2. Loki Bugzilla (Fenris)</H1

14109

>D.2. Loki Bugzilla (Fenris)</A

14110

></H2

12856

14111

><P

12857

14112

>Fenris was a fork from Bugzilla made by Loki Games; when

12858

14113

Loki went into receivership, it died. While Loki's other code lives on,

12863

14118

></DIV

12864

14119

><DIV

12865

14120

CLASS="section"

12866

><HR><H1

14121

><HR><H2

12867

14122

CLASS="section"

12868

14123

><A

12869

14124

NAME="variant-issuezilla"

12870

></A

12871

>D.3. Issuezilla</H1

14125

>D.3. Issuezilla</A

14126

></H2

12872

14127

><P

12873

14128

>Issuezilla was another fork from Bugzilla, made by collab.net and

12874

14129

hosted at tigris.org. It is also dead; the primary focus of bug-tracking

12882

14137

></DIV

12883

14138

><DIV

12884

14139

CLASS="section"

12885

><HR><H1

14140

><HR><H2

12886

14141

CLASS="section"

12887

14142

><A

12888

14143

NAME="variant-scarab"

12889

></A

12890

>D.4. Scarab</H1

14144

>D.4. Scarab</A

14145

></H2

12891

14146

><P

12892

14147

>Scarab is a new open source bug-tracking system built using Java

12893

14148

Servlet technology. It is currently at version 1.0 beta 13.</P

12904

14159

></DIV

12905

14160

><DIV

12906

14161

CLASS="section"

12907

><HR><H1

14162

><HR><H2

12908

14163

CLASS="section"

12909

14164

><A

12910

14165

NAME="variant-perforce"

12911

></A

12912

>D.5. Perforce SCM</H1

14166

>D.5. Perforce SCM</A

14167

></H2

12913

14168

><P

12914

14169

>Although Perforce isn't really a bug tracker, it can be used as

12915

14170

such through the <SPAN

12931

14186

></DIV

12932

14187

><DIV

12933

14188

CLASS="section"

12934

><HR><H1

14189

><HR><H2

12935

14190

CLASS="section"

12936

14191

><A

12937

14192

NAME="variant-sourceforge"

12938

></A

12939

>D.6. SourceForge</H1

14193

>D.6. SourceForge</A

14194

></H2

12940

14195

><P

12941

14196

>SourceForge is a way of coordinating geographically

12942

14197

distributed free software and open source projects over the Internet.

12963

14218

><P

12964

14219

>Version 1.1, March 2000</P

12965

14220

><A

12966

NAME="AEN2290"

14221

NAME="AEN2503"

12967

14222

></A

12968

14223

><BLOCKQUOTE

12969

14224

CLASS="BLOCKQUOTE"

12975

14230

></BLOCKQUOTE

12976

14231

><DIV

12977

14232

CLASS="section"

12978

><HR><H1

14233

><HR><H2

12979

14234

CLASS="section"

12980

14235

><A

12981

14236

NAME="gfdl-0"

12982

></A

12983

>0. PREAMBLE</H1

14237

>0. PREAMBLE</A

14238

></H2

12984

14239

><P

12985

14240

>The purpose of this License is to make a manual, textbook, or other

12986

14241

written document "free" in the sense of freedom: to assure everyone the

13005

14260

></DIV

13006

14261

><DIV

13007

14262

CLASS="section"

13008

><HR><H1

14263

><HR><H2

13009

14264

CLASS="section"

13010

14265

><A

13011

14266

NAME="gfdl-1"

13012

></A

13013

>1. APPLICABILITY AND DEFINITIONS</H1

14267

>1. APPLICABILITY AND DEFINITIONS</A

14268

></H2

13014

14269

><P

13015

14270

>This License applies to any manual or other work that contains a

13016

14271

notice placed by the copyright holder saying it can be distributed under

13070

14325

></DIV

13071

14326

><DIV

13072

14327

CLASS="section"

13073

><HR><H1

14328

><HR><H2

13074

14329

CLASS="section"

13075

14330

><A

13076

14331

NAME="gfdl-2"

13077

></A

13078

>2. VERBATIM COPYING</H1

14332

>2. VERBATIM COPYING</A

14333

></H2

13079

14334

><P

13080

14335

>You may copy and distribute the Document in any medium, either

13081

14336

commercially or noncommercially, provided that this License, the

13092

14347

></DIV

13093

14348

><DIV

13094

14349

CLASS="section"

13095

><HR><H1

14350

><HR><H2

13096

14351

CLASS="section"

13097

14352

><A

13098

14353

NAME="gfdl-3"

13099

></A

13100

>3. COPYING IN QUANTITY</H1

14354

>3. COPYING IN QUANTITY</A

14355

></H2

13101

14356

><P

13102

14357

>If you publish printed copies of the Document numbering more than

13103

14358

100, and the Document's license notice requires Cover Texts, you must

13136

14391

></DIV

13137

14392

><DIV

13138

14393

CLASS="section"

13139

><HR><H1

14394

><HR><H2

13140

14395

CLASS="section"

13141

14396

><A

13142

14397

NAME="gfdl-4"

13143

></A

13144

>4. MODIFICATIONS</H1

14398

>4. MODIFICATIONS</A

14399

></H2

13145

14400

><P

13146

14401

>You may copy and distribute a Modified Version of the Document

13147

14402

under the conditions of sections 2 and 3 above, provided that you release

13274

14529

></DIV

13275

14530

><DIV

13276

14531

CLASS="section"

13277

><HR><H1

14532

><HR><H2

13278

14533

CLASS="section"

13279

14534

><A

13280

14535

NAME="gfdl-5"

13281

></A

13282

>5. COMBINING DOCUMENTS</H1

14536

>5. COMBINING DOCUMENTS</A

14537

></H2

13283

14538

><P

13284

14539

>You may combine the Document with other documents released under

13285

14540

this License, under the terms defined in section 4 above for modified

13305

14560

></DIV

13306

14561

><DIV

13307

14562

CLASS="section"

13308

><HR><H1

14563

><HR><H2

13309

14564

CLASS="section"

13310

14565

><A

13311

14566

NAME="gfdl-6"

13312

></A

13313

>6. COLLECTIONS OF DOCUMENTS</H1

14567

>6. COLLECTIONS OF DOCUMENTS</A

14568

></H2

13314

14569

><P

13315

14570

>You may make a collection consisting of the Document and other

13316

14571

documents released under this License, and replace the individual copies

13326

14581

></DIV

13327

14582

><DIV

13328

14583

CLASS="section"

13329

><HR><H1

14584

><HR><H2

13330

14585

CLASS="section"

13331

14586

><A

13332

14587

NAME="gfdl-7"

13333

></A

13334

>7. AGGREGATION WITH INDEPENDENT WORKS</H1

14588

>7. AGGREGATION WITH INDEPENDENT WORKS</A

14589

></H2

13335

14590

><P

13336

14591

>A compilation of the Document or its derivatives with other

13337

14592

separate and independent documents or works, in or on a volume of a

13350

14605

></DIV

13351

14606

><DIV

13352

14607

CLASS="section"

13353

><HR><H1

14608

><HR><H2

13354

14609

CLASS="section"

13355

14610

><A

13356

14611

NAME="gfdl-8"

13357

></A

13358

>8. TRANSLATION</H1

14612

>8. TRANSLATION</A

14613

></H2

13359

14614

><P

13360

14615

>Translation is considered a kind of modification, so you may

13361

14616

distribute translations of the Document under the terms of section 4.

13370

14625

></DIV

13371

14626

><DIV

13372

14627

CLASS="section"

13373

><HR><H1

14628

><HR><H2

13374

14629

CLASS="section"

13375

14630

><A

13376

14631

NAME="gfdl-9"

13377

></A

13378

>9. TERMINATION</H1

14632

>9. TERMINATION</A

14633

></H2

13379

14634

><P

13380

14635

>You may not copy, modify, sublicense, or distribute the Document

13381

14636

except as expressly provided for under this License. Any other attempt to

13387

14642

></DIV

13388

14643

><DIV

13389

14644

CLASS="section"

13390

><HR><H1

14645

><HR><H2

13391

14646

CLASS="section"

13392

14647

><A

13393

14648

NAME="gfdl-10"

13394

></A

13395

>10. FUTURE REVISIONS OF THIS LICENSE</H1

14649

>10. FUTURE REVISIONS OF THIS LICENSE</A

14650

></H2

13396

14651

><P

13397

14652

>The Free Software Foundation may publish new, revised versions of

13398

14653

the GNU Free Documentation License from time to time. Such new versions

13417

14672

></DIV

13418

14673

><DIV

13419

14674

CLASS="section"

13420

><HR><H1

14675

><HR><H2

13421

14676

CLASS="section"

13422

14677

><A

13423

14678

NAME="gfdl-howto"

13424

></A

13425

>How to use this License for your documents</H1

14679

>How to use this License for your documents</A

14680

></H2

13426

14681

><P

13427

14682

>To use this License in a document you have written, include a copy

13428

14683

of the License in the document and put the following copyright and

13429

14684

license notices just after the title page:</P

13430

14685

><A

13431

NAME="AEN2380"

14686

NAME="AEN2593"

13432

14687

></A

13433

14688

><BLOCKQUOTE

13434

14689

CLASS="BLOCKQUOTE"

13465

14720

><H1

13466

14721

CLASS="glossdiv"

13467

14722

><A

13468

NAME="AEN2385"

13469

></A

13470

>0-9, high ascii</H1

14723

NAME="AEN2598"

14724

>0-9, high ascii</A

14725

></H1

13471

14726

><DL

13472

14727

><DT

13473

14728

><B

13500

14755

CLASS="glossdiv"

13501

14756

><A

13502

14757

NAME="gloss-a"

13503

></A

13504

>A</H1

14758

>A</A

14759

></H1

13505

14760

><DL

13506

14761

><DT

13507

14762

><B

13525

14780

>

13526

14781

13527

14782

version of the original

13528

<SPAN

14783

<ACRONYM

13529

14784

CLASS="acronym"

13530

>NCSA</SPAN

14785

>NCSA</ACRONYM

13531

14786

>

13532

14787

13533

14788

world-wide-web server.</P

13541

14796

></P

13542

14797

><DL

13543

14798

><DT

13544

><TT

14799

><SAMP

13545

14800

CLASS="computeroutput"

13546

14801

><A

13547

14802

HREF="http://httpd.apache.org/docs-2.0/mod/core.html#addhandler"

13548

14803

TARGET="_top"

13549

14804

>AddHandler</A

13550

></TT

14805

></SAMP

13551

14806

></DT

13552

14807

><DD

13553

14808

><P

13554

14809

>Tell Apache that it's OK to run CGI scripts.</P

13555

14810

></DD

13556

14811

><DT

13557

><TT

14812

><SAMP

13558

14813

CLASS="computeroutput"

13559

14814

><A

13560

14815

HREF="http://httpd.apache.org/docs-2.0/mod/core.html#allowoverride"

13561

14816

TARGET="_top"

13562

14817

>AllowOverride</A

13563

></TT

13564

>, <TT

14818

></SAMP

14819

>, <SAMP

13565

14820

CLASS="computeroutput"

13566

14821

><A

13567

14822

HREF="http://httpd.apache.org/docs-2.0/mod/core.html#options"

13568

14823

TARGET="_top"

13569

14824

>Options</A

13570

></TT

14825

></SAMP

13571

14826

></DT

13572

14827

><DD

13573

14828

><P

13581

14836

</P

13582

14837

></DD

13583

14838

><DT

13584

><TT

14839

><SAMP

13585

14840

CLASS="computeroutput"

13586

14841

><A

13587

14842

HREF="http://httpd.apache.org/docs-2.0/mod/mod_dir.html#directoryindex"

13588

14843

TARGET="_top"

13589

14844

>DirectoryIndex</A

13590

></TT

14845

></SAMP

13591

14846

></DT

13592

14847

><DD

13593

14848

><P

13596

14851

CLASS="filename"

13597

14852

>index.cgi</TT

13598

14853

> to the list of valid files,

13599

you'll need to set <TT

14854

you'll need to set <SAMP

13600

14855

CLASS="computeroutput"

13601

>$index_html</TT

14856

>$index_html</SAMP

13602

14857

> to

13603

14858

1 in <TT

13604

14859

CLASS="filename"

13619

14874

</P

13620

14875

></DD

13621

14876

><DT

13622

><TT

14877

><SAMP

13623

14878

CLASS="computeroutput"

13624

14879

><A

13625

14880

HREF="http://httpd.apache.org/docs-2.0/mod/core.html#scriptinterpretersource"

13626

14881

TARGET="_top"

13627

14882

>ScriptInterpreterSource</A

13628

></TT

14883

></SAMP

13629

14884

></DT

13630

14885

><DD

13631

14886

><P

13644

14899

CLASS="glossdiv"

13645

14900

><A

13646

14901

NAME="gloss-b"

13647

></A

13648

>B</H1

14902

>B</A

14903

></H1

13649

14904

><DL

13650

14905

><DT

13651

14906

><B

13703

14958

CLASS="glossdiv"

13704

14959

><A

13705

14960

NAME="gloss-c"

13706

></A

13707

>C</H1

14961

>C</A

14962

></H1

13708

14963

><DL

13709

14964

><DT

13710

14965

><A

13715

14970

></DT

13716

14971

> (CGI)<DD

13717

14972

><P

13718

><SPAN

14973

><ACRONYM

13719

14974

CLASS="acronym"

13720

>CGI</SPAN

14975

>CGI</ACRONYM

13721

14976

> is an acronym for Common Gateway Interface.

13722

14977

This is a standard for interfacing an external application with a web

13723

server. Bugzilla is an example of a <SPAN

14978

server. Bugzilla is an example of a <ACRONYM

13724

14979

CLASS="acronym"

13725

>CGI</SPAN

14980

>CGI</ACRONYM

13726

14981

> application.

13727

14982

</P

13728

14983

></DD

13745

15000

NAME="gloss-cpan"

13746

15001

></A

13747

15002

><B

13748

> <SPAN

15003

> <ACRONYM

13749

15004

CLASS="acronym"

13750

>CPAN</SPAN

15005

>CPAN</ACRONYM

13751

15006

>

13752

15007

</B

13753

15008

></DT

13754

15009

><DD

13755

15010

><P

13756

> <SPAN

15011

> <ACRONYM

13757

15012

CLASS="acronym"

13758

>CPAN</SPAN

15013

>CPAN</ACRONYM

13759

15014

>

13760

15015

13761

15016

stands for the

13779

15034

CLASS="glossdiv"

13780

15035

><A

13781

15036

NAME="gloss-d"

13782

></A

13783

>D</H1

15037

>D</A

15038

></H1

13784

15039

><DL

13785

15040

><DT

13786

15041

><B

13810

15065

CLASS="glossdiv"

13811

15066

><A

13812

15067

NAME="gloss-g"

13813

></A

13814

>G</H1

15068

>G</A

15069

></H1

13815

15070

><DL

13816

15071

><DT

13817

15072

><B

13847

15102

CLASS="glossdiv"

13848

15103

><A

13849

15104

NAME="gloss-m"

13850

></A

13851

>M</H1

15105

>M</A

15106

></H1

13852

15107

><DL

13853

15108

><DT

13854

15109

><A

13871

15126

>/usr/sbin/sendmail</TT

13872

15127

>.

13873

15128

Many other MTA's will work, but they all require that the

13874

<TT

15129

<VAR

13875

15130

CLASS="option"

13876

>sendmailnow</TT

13877

> param be set to <TT

15131

>sendmailnow</VAR

15132

> param be set to <VAR

13878

15133

CLASS="literal"

13879

>on</TT

15134

>on</VAR

13880

15135

>.

13881

15136

</P

13882

15137

></DD

13932

15187

CLASS="glossdiv"

13933

15188

><A

13934

15189

NAME="gloss-p"

13935

></A

13936

>P</H1

15190

>P</A

15191

></H1

13937

15192

><DL

13938

15193

><DT

13939

15194

><B

13972

15227

CLASS="glossdiv"

13973

15228

><A

13974

15229

NAME="gloss-q"

13975

></A

13976

>Q</H1

15230

>Q</A

15231

></H1

13977

15232

><DL

13978

15233

><DT

13979

15234

><B

14017

15272

CLASS="glossdiv"

14018

15273

><A

14019

15274

NAME="gloss-r"

14020

></A

14021

>R</H1

15275

>R</A

15276

></H1

14022

15277

><DL

14023

15278

><DT

14024

15279

><A

14041

15296

CLASS="glossdiv"

14042

15297

><A

14043

15298

NAME="gloss-s"

14044

></A

14045

>S</H1

15299

>S</A

15300

></H1

14046

15301

><DL

14047

15302

><DT

14048

15303

><B

14049

> <SPAN

15304

> <ACRONYM

14050

15305

CLASS="acronym"

14051

>SGML</SPAN

15306

>SGML</ACRONYM

14052

15307

>

14053

15308

</B

14054

15309

></DT

14055

15310

><DD

14056

15311

><P

14057

> <SPAN

15312

> <ACRONYM

14058

15313

CLASS="acronym"

14059

>SGML</SPAN

15314

>SGML</ACRONYM

14060

15315

>

14061

15316

14062

15317

stands for

14066

15321

>.

14067

15322

Created in the 1980's to provide an extensible means to maintain

14068

15323

documentation based upon content instead of presentation,

14069

<SPAN

15324

<ACRONYM

14070

15325

CLASS="acronym"

14071

>SGML</SPAN

15326

>SGML</ACRONYM

14072

15327

>

14073

15328

14074

15329

has withstood the test of time as a robust, powerful language.

14075

15330

<I

14076

15331

CLASS="glossterm"

14077

> <SPAN

15332

> <ACRONYM

14078

15333

CLASS="acronym"

14079

>XML</SPAN

15334

>XML</ACRONYM

14080

15335

>

14081

15336

</I

14082

15337

>

14088

15343

>

14089

15344

14090

15345

of SGML; any valid

14091

<SPAN

15346

<ACRONYM

14092

15347

CLASS="acronym"

14093

>XML</SPAN

15348

>XML</ACRONYM

14094

15349

>

14095

15350

14096

15351

document it, by definition, a valid

14097

<SPAN

15352

<ACRONYM

14098

15353

CLASS="acronym"

14099

>SGML</SPAN

15354

>SGML</ACRONYM

14100

15355

>

14101

15356

14102

15357

document. The document you are reading is written and maintained in

14103

<SPAN

15358

<ACRONYM

14104

15359

CLASS="acronym"

14105

>SGML</SPAN

15360

>SGML</ACRONYM

14106

15361

>,

14107

15362

and is also valid

14108

<SPAN

15363

<ACRONYM

14109

15364

CLASS="acronym"

14110

>XML</SPAN

15365

>XML</ACRONYM

14111

15366

>

14112

15367

14113

15368

if you modify the Document Type Definition.</P

14120

15375

CLASS="glossdiv"

14121

15376

><A

14122

15377

NAME="gloss-t"

14123

></A

14124

>T</H1

15378

>T</A

15379

></H1

14125

15380

><DL

14126

15381

><DT

14127

15382

><A

14168

15423

CLASS="glossdiv"

14169

15424

><A

14170

15425

NAME="gloss-z"

14171

></A

14172

>Z</H1

15426

>Z</A

15427

></H1

14173

15428

><DL

14174

15429

><DT

14175

15430

><A

14185

15440

Terry had the following to say:

14186

15441

</P

14187

15442

><A

14188

NAME="AEN2579"

15443

NAME="AEN2792"

14189

15444

></A

14190

15445

><TABLE

14191

15446

BORDER="0"

14199

15454

VALIGN="TOP"

14200

15455

> </TD

14201

15456

><TD

14202

WIDTH="80%"

14203

15457

VALIGN="TOP"

14204

15458

><P

14205

15459

>I've been asked to explain this ... way back when, when