/usr/share/doc/refdb/refdb-manual/ch05s08.html is in refdb-doc 1.0.2-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 | <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>How to run several refdb instances</title><link rel="stylesheet" type="text/css" href="manual.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /><link rel="home" href="index.html" title="RefDB handbook" /><link rel="up" href="ch05.html" title="Chapter 5. refdbd administration" /><link rel="prev" href="ch05s07.html" title="Security issues" /><link rel="next" href="ch05s09.html" title="Backup your data" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">How to run several refdb instances</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch05s07.html">Prev</a> </td><th width="60%" align="center">Chapter 5. refdbd administration</th><td width="20%" align="right"> <a accesskey="n" href="ch05s09.html">Next</a></td></tr></table><hr /></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="idp66748320"></a>How to run several refdb instances</h2></div></div></div><p>In all but a few cases, having one refdbd daemon per network is absolutely sufficient. However, there are a few cases where you may end up running more than one instance of refdbd on the same computer at the same time:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>You want to provide access to more than one database engine. The only good reason to do this may be to test-drive a different database engine.</p></li><li class="listitem"><p>You want to test-drive a new refdb release without interrupting the access to your installed version</p></li><li class="listitem"><p>You do not want to run refdbd as a daemon serving all users. Instead, each user should be able to run his own copy of refdbd</p></li></ul></div><p>You'll have to configure each refdbd process individually. If each user starts his own copy of the application server, private <code class="filename">.refdbdrc</code> configuration files in the users' <code class="envar">$HOME</code> directory allow a simple setup. If you want to run more than one daemon as non-user-processes, you cannot safely use the <span class="command"><strong>refdbctl</strong></span> script to control the instances. Instead you should start and stop the daemons manually and use the appropriate command-line options to configure each process individually. The options which need to be set differently whenever more than one refdbd instance runs on the same box are:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><code class="option">-D</code>, <code class="option">-i</code>, and<code class="option">-b</code> to set the database engine, IP address, and the port it listens on, respectively. Only required if you fiddle with two different database engines.</p></li><li class="listitem"><p><code class="option">-e</code> and <em class="parameter"><code>-L</code></em> to use separate log files for the two instances. This may be easier to evaluate than using syslog, although the processes can be distinguished by means of their process ID.</p></li><li class="listitem"><p><code class="option">-P</code> to use separate PID files</p></li><li class="listitem"><p><code class="option">-p</code> to set the port each refdbd instance listens on. The ports must be different, otherwise clients can't select which instance to connect to.</p></li></ul></div><p>On the client side you'll need only set the <code class="varname">port</code> configuration variable or use the <code class="option">-p</code> command line option to select the application server instance that you want to connect to.</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch05s07.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch05.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch05s09.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Security issues </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Backup your data</td></tr></table></div></body></html>
|