The ogclean tool can be used to clean up any stray lockfiles that correspond to OneGate processes that are no longer running.

Sometimes during development, people generate program sets that hang indefinitely at the command level, and then kill off the jobs and the OneGate sessions. While OneGate traps the common termination signals and cleans its lock files in most instances, signal 9 in *nix (SIGKILL), for example, is entirely untrappable. Using such brute force would result in a stranded lockfile that would be taking up one "slot" in the maximum session count.

This tool is meant to be run either manually or from cron (or a task scheduler in Windows, if needed), and will remove any lockfiles corresponding to processes that are no longer running.

You simply invoke the program by calling ogclean with no arguments, and it cleans any stray lockfiles. You will be notified of any lockfiles removed. If you wish to cause the program to always run silently, simply create the file [maindir]/quietclean to achieve this effect. That file's presence suppresses the usual non-error output of the lock cleaning program. This file need only be placed in the original installation [maindir], not any testbed versions of [maindir], as all locking is handled from the installation site to make session counts work correctly.