For more information... RTFM!
NAVIGATION
RECENTLY VIEWED
PAGES THAT LINK HERE
ACCOUNT LOGIN

You are not logged in

Powered by Interchange version 5.7.0

PIDcheck

Periodically kill Interchange child processes, allowing then to respawn afresh.

Synopsis

PIDcheck  interval

The parameter is expected to be a time interval.  The default is 0 (disabled).

Scope

This directive is only available for use in the global (interchange.cfg) configuration file, and will affect all websites running under the Interchange installation.  It will not work in a website's local (catalog.cfg) configuration file. 

Description

If non-zero, this directive enables a check of running Interchange processes during the HouseKeeping routine.  If a process has been running (or is hung) for longer than PIDcheck seconds then a "kill -9" will be issued and the server count will be decremented.  The number of available servers will be recounted, with the count based upon the number of PID files, during the HouseKeeping routine.

If a process is killed by Interchange, using this facility, then the incident will be logged to the global "error.log" file, as follows:

Hammered PID 12345 running 600 seconds.

If you have long-running database builds or imports etc., this needs to be disabled (set to 0) or set to a high value (perhaps 600, for 10 minutes).

You should also take a look at the ChildLife global configuration directive.

Examples

You may specify the time in seconds: 

PIDcheck  300

You may also specify the time using an Interchange time interval string: 

PIDcheck  5 minutes

The check may be disabled (which is the default anyway) like this: 

PIDcheck  0

Category:  Global config directives
Last modified by: Kevin Walsh
Modification date: Wednesday 27 June 2007 at 5:29 AM (EDT)

Donations

Please contact us if you have a HOWTO-style document, or anything else you'd like to share with other Interchange users and developers.  Go on - you know you want to.

Home  |  Legal nonsense  |  Privacy policy  |  Contact us