[docs] xmldocs - docelic modified 4 files
docs at icdevgroup.org
docs at icdevgroup.org
Sat Oct 30 08:32:56 EDT 2004
User: docelic
Date: 2004-10-30 12:32:56 GMT
Added: refs HouseKeeping PIDcheck PIDfile SocketPerms
Log:
New items
Revision Changes Path
1.1 xmldocs/refs/HouseKeeping
rev 1.1, prev_rev 1.0
Index: HouseKeeping
===================================================================
__NAME__ purpose
number of seconds between periodic "house keeping" jobs
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain'>seconds</arg>
</group>
__END__
__NAME__ description
Specify how often, in seconds, the Interchange server will "wake up" and
look for user reconfiguration requests and hung search processes. On some
systems, this wakeup is the only time the server will terminate in response
to a stop command.
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
HouseKeepign 5
</programlisting>
</example>
__END__
1.1 xmldocs/refs/PIDcheck
rev 1.1, prev_rev 1.0
Index: PIDcheck
===================================================================
__NAME__ purpose
check running Interchange processes during the HouseKeeping routine
__END__
__NAME__ see also
HouseKeeping
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain'>0</arg>
<arg choice='plain'>seconds</arg>
</group>
__END__
__NAME__ description
If set to a positive non-zero value, enables check of running
Interchange processes during the <option>HouseKeeping</option> routine.
</para><para>
If a process has been running (or is hung) for longer than
<option>PIDcheck</option> seconds, then <userinput>kill -9</userinput> will
be issued and the server count decremented.
</para><para>
During the HouseKeeping routine,
the number of servers checked by <option>MaxServers</option> will be
recounted based on PID files.
__END__
__NAME__ missing
The comment on MaxServers is confusing.
__END__
__NAME__ notes
If you have long-running database builds, this directive needs to stay
disabled, or set to a high value (of perhaps <literal>600</literal>, or
<literal>10 minutes</literal>), or use the <command>bin/offline</command>
script.
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
PIDcheck 300
</programlisting>
</example>
__END__
1.1 xmldocs/refs/PIDfile
rev 1.1, prev_rev 1.0
Index: PIDfile
===================================================================
__NAME__ purpose
PID filename
__END__
__NAME__ see also
PIDcheck
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain'>filename</arg>
</group>
__END__
__NAME__ description
Specify the filename that will contain Interchange server process ID. As with
most Unix daemons, this is an elegant way to determine which process should
be sent a signal for stopping or reconfiguring the server.
</para><para>
The location must be writable by the Interchange daemon.
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
PIDfile /var/run/interchange/interchange.pid
</programlisting>
</example>
__END__
1.1 xmldocs/refs/SocketPerms
rev 1.1, prev_rev 1.0
Index: SocketPerms
===================================================================
__NAME__ purpose
Interchange Unix socket permissions
__END__
__NAME__ see also
SocketFile
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain'>mode</arg>
</group>
__END__
__NAME__ description
Specify permissions (&mode;) for the Interchange UNIX-domain socket.
</para><para>
Prepend a starting <literal>0</literal> to indicate an octal value.
__END__
__NAME__ notes
Although not recommended in practice, it sometimes makes sense to
set the permissions to <literal>0666</literal> (world-writable) to
easier debug problems.
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
SocketPerms 0666
</programlisting>
</example>
__END__
More information about the docs
mailing list