You are not allowed to run any server process (including a Web
server) on CS machines outside the burrow without the sponsorship
of a member of the faculty. The burrow cluster is provided as
a playground of sorts for things that are not otherwise allowed.
We have a server as part of the burrow cluster named silo
(aka. silo.cs.indiana.edu) where you can run your web servers,
complete with CGI, PHP, or anything else you want to play with.
All CS faculty, students, and staff are eligible
for a burrow account.
If you plan to run a server in the burrow please use the
machine named silo.cs.indiana.edu
and please keep in mind
that the setup and maintenance is entirely your responsibility.
Servers must be registered, however, so they don't compete for the same ports.
Register servers by e-mailing systems staff at
sysadm with the desired service,
software, port and purpose. Please do not ask us to assign a port for you. Just
pick a port yourself, but do let us know what pick. You can
pick any unused port number in the range 1025-65535. Use the checkport
command to verify that the port number you have selected is not already
reserved or in use. For example, if you run "checkport 34345" on silo,
it will report whether port 34345 is available or not.
If you want to run apache using the pre-installed version of apache
that comes with the OS, this can be done very simply as described
in the associated FAQ entry.
If you are are using the apache web server, or any other web server that
relies on a lock file, YOU MUST MAKE SURE YOU PROPERLY CONFIGURE THE
LockFile DIRECTIVE. By default, apache will create a lock file in
your home directory. This causes problems because this lock file should
never reside on a network file system (via NFS), which is exactly where
your home directory resides. To prevent this problem,
please add something like
LockFile /tmp/.apache.lock.username
to your apache configuration file, httpd.conf. For more information about this
problem, please search for "LockFile" in the apache documentation.
CS reserves the right to reject or discontinue any services
or content that are not compatible with the purposes of the Burrow or
the goals of the department. Services may also be discontinued if
they overload the facilities, introduce security vulnerabilities, are
not adequately maintained, or otherwise lead to problems. Services may
be required to be relocated at the request of systems staff. While the
privacy of user files is respected as on all CS systems, systems staff
reserves the right to inspect and modify user files related to a Burrow
server if necessary to correct or subdue a problem with the server.
