Tracing System Resource Cleanup Operations

Using the JUNOS SDK, developers can have their SDK applications request and manage system resources.

Some of this resource utilization is persistent across, for example, reboots or the restart of the application. And some system tasks such as deleting a package, disabling an application, or accessing shared resources require that resources be cleaned up by entities other than the application itself. Resources that are known to need cleaning up include the following:

As of JUNOS Release 9.3, the traceoptions statement is the only CLI statement available for configuring resource cleanup. To turn on or off debugging trace messages, use the flag option.

system {
    processes {
        resource-cleanup {
            traceoptions {
                file filename <files number> <match regular-expression> <size maximum-file-size> <world-readable | no-world-readable>;
                flag flag;
                level (all | error | info | notice | verbose | warning);

You can configure one or more of the following flags:

Other Configuration Guidelines:
Guidelines for Configuring SDK Applications

See also:
Statement Summary

Configuration Command Summary

Operational Command Reference

SDK CLI Configuration

2007-2009 Juniper Networks, Inc. All rights reserved. The information contained herein is confidential information of Juniper Networks, Inc., and may not be used, disclosed, distributed, modified, or copied without the prior written consent of Juniper Networks, Inc. in an express license. This information is subject to change by Juniper Networks, Inc. Juniper Networks, the Juniper Networks logo, and JUNOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Generated on Sun May 30 20:26:48 2010 for Juniper Networks Partner Solution Development Platform JUNOS SDK 10.2R1 by Doxygen 1.4.5