A brief treatise on the timeouts used by Quipu systems.


A Quipu DSA has various timeouts:

admintime:	default 2 minutes
	This is the maximum time A DSA is prepared to spend processing
	any one DAP/DSP operation.

cachetime:	default 6 hours
	The maximum length of time a DSA is prepared to used 'cached' 
	information.  After this time the cache is discarded.

slavetime:	default the same as cachetime (thus if you alter cachetime,
		by default you are altering this as well)
	The time between updates of slave EDB files.

retrytime:	default the same as cachetime
	A DSA keeps track of all failed connections, and if possible avoids
	using that DSA besause it is considered unreliable.
	This unreliability information is discarded after 'retrytime'.

conntime:	default 5 minutes
	The length of time to hold open a DSP connection after an operation
	has completed.

nsaptime:	45 seconds
	The length of time to wait before deciding a connection can not be 
	established on a given NSAP address.


All of these can all be tailored in 'quiputailor'.
All times must be given in seconds.
For example to alter the 'conntime' to 2 mintues use:
	conntime 	120




A DUA (by default, specific DUAs may change this) has just one timeout:

timelimit:	default 30 seconds
	The maximum time a DSA should spend processing a query from
	the DUA.

This can be tailored in 'dsaptailor'.
If you are using dish, this can be altered on the command line e.g
	list -timelimit 120




Dish has a two other timeouts:

cache_time:	default 6 hours
	The length of time a background dish process will stay alive
	(to maintain its cache) after an operation.

connect_time:	default 2 minutes
	'connect_time' after an operation dish will issue an automatic
	DAP unbind.

These are tailorable in HOME/.quipurc



Colin Robbins