<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>2.6. UNIX (non-root) Installation Notes</title><link rel="stylesheet" type="text/css" href="../../style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><meta name="keywords" content="Bugzilla, Guide, installation, FAQ, administration, integration, MySQL, Mozilla, webtools"><link rel="home" href="index.html" title="The Bugzilla Guide - 4.4.11 Release"><link rel="up" href="installing-bugzilla.html" title="Chapter 2. Installing Bugzilla"><link rel="prev" href="os-specific.html" title="2.5. OS-Specific Installation Notes"><link rel="next" href="upgrade.html" title="2.7. Upgrading to New Releases"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.6. UNIX (non-root) Installation Notes</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="os-specific.html">Prev</a> </td><th width="60%" align="center">Chapter 2. Installing Bugzilla</th><td width="20%" align="right"> <a accesskey="n" href="upgrade.html">Next</a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="nonroot"></a>2.6. UNIX (non-root) Installation Notes</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140035937821408"></a>2.6.1. Introduction</h3></div></div></div><p>If you are running a *NIX OS as non-root, either due
to lack of access (web hosts, for example) or for security
reasons, this will detail how to install Bugzilla on such
a setup. It is recommended that you read through the
<a class="xref" href="installation.html" title="2.1. Installation">Section 2.1, “Installation”</a>
first to get an idea on the installation steps required.
(These notes will reference to steps in that guide.)</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140035937819168"></a>2.6.2. MySQL</h3></div></div></div><p>You may have MySQL installed as root. If you're
setting up an account with a web host, a MySQL account
needs to be set up for you. From there, you can create
the bugs account, or use the account given to you.</p><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>You may have problems trying to set up
<span class="command"><strong>GRANT</strong></span> permissions to the database.
If you're using a web host, chances are that you have a
separate database which is already locked down (or one big
database with limited/no access to the other areas), but you
may want to ask your system administrator what the security
settings are set to, and/or run the <span class="command"><strong>GRANT</strong></span>
command for you.</p><p>Also, you will probably not be able to change the MySQL
root user password (for obvious reasons), so skip that
step.</p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140035937814576"></a>2.6.2.1. Running MySQL as Non-Root</h4></div></div></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140035937813824"></a>2.6.2.1.1. The Custom Configuration Method</h5></div></div></div><p>Create a file .my.cnf in your
home directory (using /home/foo in this example)
as follows....</p><pre class="programlisting">
[mysqld]
datadir=/home/foo/mymysql
socket=/home/foo/mymysql/thesock
port=8081
[mysql]
socket=/home/foo/mymysql/thesock
port=8081
[mysql.server]
user=mysql
basedir=/var/lib
[safe_mysqld]
err-log=/home/foo/mymysql/the.log
pid-file=/home/foo/mymysql/the.pid
</pre></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140035937811376"></a>2.6.2.1.2. The Custom Built Method</h5></div></div></div><p>You can install MySQL as a not-root, if you really need to.
Build it with PREFIX set to <code class="filename">/home/foo/mysql</code>,
or use pre-installed executables, specifying that you want
to put all of the data files in <code class="filename">/home/foo/mysql/data</code>.
If there is another MySQL server running on the system that you
do not own, use the -P option to specify a TCP port that is not
in use.</p></div><div class="section"><div class="titlepage"><div><div><h5 class="title"><a name="idm140035937807712"></a>2.6.2.1.3. Starting the Server</h5></div></div></div><p>After your mysqld program is built and any .my.cnf file is
in place, you must initialize the databases (ONCE).</p><pre class="screen">
<code class="prompt">bash$</code> <span class="command"><strong>mysql_install_db</strong></span>
</pre><p>Then start the daemon with</p><pre class="screen">
<code class="prompt">bash$</code> <span class="command"><strong>safe_mysql &</strong></span>
</pre><p>After you start mysqld the first time, you then connect to
it as "root" and <span class="command"><strong>GRANT</strong></span> permissions to other
users. (Again, the MySQL root account has nothing to do with
the *NIX root account.)</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>You will need to start the daemons yourself. You can either
ask your system administrator to add them to system startup files, or
add a crontab entry that runs a script to check on these daemons
and restart them if needed.</p></td></tr></table></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Do NOT run daemons or other services on a server without first
consulting your system administrator! Daemons use up system resources
and running one may be in violation of your terms of service for any
machine on which you are a user!</p></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140035937797488"></a>2.6.3. Perl</h3></div></div></div><p>
On the extremely rare chance that you don't have Perl on
the machine, you will have to build the sources
yourself. The following commands should get your system
installed with your own personal version of Perl:
</p><pre class="screen">
<code class="prompt">bash$</code> <span class="command"><strong>wget http://perl.org/CPAN/src/stable.tar.gz</strong></span>
<code class="prompt">bash$</code> <span class="command"><strong>tar zvxf stable.tar.gz</strong></span>
<code class="prompt">bash$</code> <span class="command"><strong>cd perl-5.8.1</strong></span>
<code class="prompt">bash$</code> <span class="command"><strong>sh Configure -de -Dprefix=/home/foo/perl</strong></span>
<code class="prompt">bash$</code> <span class="command"><strong>make && make test && make install</strong></span>
</pre><p>
Once you have Perl installed into a directory (probably
in <code class="filename">~/perl/bin</code>), you will need to
install the Perl Modules, described below.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="install-perlmodules-nonroot"></a>2.6.4. Perl Modules</h3></div></div></div><p>
Installing the Perl modules as a non-root user is accomplished by
running the <code class="filename">install-module.pl</code>
script. For more details on this script, see
<a class="ulink" href="../html/api/install-module.html" target="_top"><code class="filename">install-module.pl</code>
documentation</a>
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140035937782656"></a>2.6.5. HTTP Server</h3></div></div></div><p>Ideally, this also needs to be installed as root and
run under a special web server account. As long as
the web server will allow the running of *.cgi files outside of a
cgi-bin, and a way of denying web access to certain files (such as a
.htaccess file), you should be good in this department.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm140035937781168"></a>2.6.5.1. Running Apache as Non-Root</h4></div></div></div><p>You can run Apache as a non-root user, but the port will need
to be set to one above 1024. If you type <span class="command"><strong>httpd -V</strong></span>,
you will get a list of the variables that your system copy of httpd
uses. One of those, namely HTTPD_ROOT, tells you where that
installation looks for its config information.</p><p>From there, you can copy the config files to your own home
directory to start editing. When you edit those and then use the -d
option to override the HTTPD_ROOT compiled into the web server, you
get control of your own customized web server.</p><div class="note" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="../images/note.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>You will need to start the daemons yourself. You can either
ask your system administrator to add them to system startup files, or
add a crontab entry that runs a script to check on these daemons
and restart them if needed.</p></td></tr></table></div><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>Do NOT run daemons or other services on a server without first
consulting your system administrator! Daemons use up system resources
and running one may be in violation of your terms of service for any
machine on which you are a user!</p></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm140035937775648"></a>2.6.6. Bugzilla</h3></div></div></div><p>
When you run <span class="command"><strong>./checksetup.pl</strong></span> to create
the <code class="filename">localconfig</code> file, it will list the Perl
modules it finds. If one is missing, go back and double-check the
module installation from <a class="xref" href="nonroot.html#install-perlmodules-nonroot" title="2.6.4. Perl Modules">Section 2.6.4, “Perl Modules”</a>,
then delete the <code class="filename">localconfig</code> file and try again.
</p><div class="warning" style="margin-left: 1em; margin-right: 1em"><table border="0" summary="Warning"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Warning]" src="../images/warning.gif"></td><th align="left"></th></tr><tr><td align="left" valign="top"><p>One option in <code class="filename">localconfig</code> you
might have problems with is the web server group. If you can't
successfully browse to the <code class="filename">index.cgi</code> (like
a Forbidden error), you may have to relax your permissions,
and blank out the web server group. Of course, this may pose
as a security risk. Having a properly jailed shell and/or
limited access to shell accounts may lessen the security risk,
but use at your own risk.</p></td></tr></table></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="suexec"></a>2.6.6.1. suexec or shared hosting</h4></div></div></div><p>If you are running on a system that uses suexec (most shared
hosting environments do this), you will need to set the
<span class="emphasis"><em>webservergroup</em></span> value in <code class="filename">localconfig</code>
to match <span class="emphasis"><em>your</em></span> primary group, rather than the one
the web server runs under. You will need to run the following
shell commands after running <span class="command"><strong>./checksetup.pl</strong></span>,
every time you run it (or modify <code class="filename">checksetup.pl</code>
to do them for you via the system() command).
</p><pre class="programlisting">
for i in docs graphs images js skins; do find $i -type d -exec chmod o+rx {} \; ; done
for i in jpg gif css js png html rdf xul; do find . -name \*.$i -exec chmod o+r {} \; ; done
find . -name .htaccess -exec chmod o+r {} \;
chmod o+x . data data/webdot
</pre><p>
Pay particular attention to the number of semicolons and dots.
They are all important. A future version of Bugzilla will
hopefully be able to do this for you out of the box.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="os-specific.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="installing-bugzilla.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="upgrade.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">2.5. OS-Specific Installation Notes </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.7. Upgrading to New Releases</td></tr></table></div></body></html>
