The CPUStats_<hostname>.txt getting the file size without being rolled over for a long operation. Is there the way to avoid that the CPUStats_<hostname>.txt becomes huge filesize?
search cancel

The CPUStats_<hostname>.txt getting the file size without being rolled over for a long operation. Is there the way to avoid that the CPUStats_<hostname>.txt becomes huge filesize?

book

Article ID: 19814

calendar_today

Updated On:

Products

CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

The CPUStats_<hostname>.txt is not rolled over by a design. However, it is not necessary for logging because the pslist.exe logs same contents to the pslistm_<hostname>.out file in the $NX_ROOT\log folder. So, it is possible to stop to update the log to the CPUStats_<hostname>.txt.

Here is the steps to stop the update of the CPUStats_<hostname>.txt.

  1. Open the $NX_ROOT\pdmconf\pdm_startup and $NX_ROOT\pdmconf\pdm_startup.tpl files in a text editor.
    Edit both files with the steps below.

  2. Edit both files Comment the line #163 and #529.

    [Around line #163]
    PDM_INFO(pdm_info,$NX_LOCAL_HOST)
    after sw_ver_ctl connects + 3

    GATHER_PSLIST(gather_pslist,$NX_LOCAL_HOST) <---Line #163
    after domsrvr connects + 5
    GATHER_LOGS_PRI(gather_logs_pri,$NX_LOCAL_HOST)

    [Around line #529]
    sw_ver_ctl
    gather_pslist  <--- Line #529
    gather_logs_pri

    # Put the semi colon ';' at the top of line in order to comment the line as follows.
    e.g.)
    ; GATHER_PSLIST(gather_pslist,$NX_LOCAL_HOST)

  3. Remove the $NX_ROOT\log\CPUStats_<hostname>.txt

  4. Recycle the Service Desk Manager service

Environment

Release:
Component: ARGIS