[docs] xmldocs - docelic modified 3 files

docs at icdevgroup.org docs at icdevgroup.org
Sat Dec 11 18:42:46 EST 2004


User:      docelic
Date:      2004-12-11 23:42:45 GMT
Modified:  refs     HouseKeeping PIDcheck
Added:     refs     HammerLock
Log:
- Documented one more directive
- Fixed some errors

Revision  Changes    Path
1.3       +3 -2      xmldocs/refs/HouseKeeping


rev 1.3, prev_rev 1.2
Index: HouseKeeping
===================================================================
RCS file: /var/cvs/xmldocs/refs/HouseKeeping,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- HouseKeeping	8 Dec 2004 12:39:58 -0000	1.2
+++ HouseKeeping	11 Dec 2004 23:42:45 -0000	1.3
@@ -5,13 +5,14 @@
 
 __NAME__ synopsis
 <group choice='req'>
-	<arg choice='plain'>seconds</arg>
+	<arg choice='plain'>interval</arg>
 </group>
 __END__
 
 
 __NAME__ description
-Specify how often, in seconds, the Interchange server will "wake up" and
+Specify at which intervals should the Interchange server 
+<emphasis>wake up</emphasis> 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.



1.3       +9 -12     xmldocs/refs/PIDcheck


rev 1.3, prev_rev 1.2
Index: PIDcheck
===================================================================
RCS file: /var/cvs/xmldocs/refs/PIDcheck,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- PIDcheck	8 Dec 2004 12:39:58 -0000	1.2
+++ PIDcheck	11 Dec 2004 23:42:45 -0000	1.3
@@ -10,7 +10,7 @@
 __NAME__ synopsis
 <group choice='req'>
 	<arg choice='plain'>0</arg>
-	<arg choice='plain'>seconds</arg>
+	<arg choice='plain'>interval</arg>
 </group>
 __END__
 
@@ -19,18 +19,9 @@
 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
+If a process has been running (or is hung) for longer than the
+specified &glos-interval;, 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
@@ -44,6 +35,12 @@
 __NAME__ example: Setting PIDcheck
 <programlisting>
 PIDcheck 300
+</programlisting>
+__END__
+
+__NAME__ example: Setting PIDcheck in time interval other than seconds
+<programlisting>
+PIDcheck 5 minutes
 </programlisting>
 __END__
 



1.1                  xmldocs/refs/HammerLock


rev 1.1, prev_rev 1.0
Index: HammerLock
===================================================================
__NAME__ purpose
number of seconds after which a locked session is considered lost due to malfunction
__END__


__NAME__ synopsis
<group choice='req'>
	<arg choice='plain'>interval</arg>
</group>
__END__


__NAME__ description
The directive specifies an interval after which a locked session could be
considered to be
lost due to malfunction. This will also clean up the session lock.
__END__

__NAME__ notes
This directive is only present to monitor session hand-offs.
If a message generated by this directive shows up in error logs, the
system setup should be examined.
</para><para>
When file-based &glos-session;s are used, this directive mostly
does not apply.
__END__

__NAME__ missing
How can HammerLock "mostly not apply" with file-based sessions?
__END__

__NAME__ example: Adjusting the HammerLock interval
<programlisting>
HammerLock 1 minute
</programlisting>
__END__









More information about the docs mailing list