Log Files

Description - ASCII files that document the status of:

Purpose - Developers and administrators use log files to diagnose installation, setup, and configuration problems.

Recommended Usage - Enable, configure, and access log files while performing Gcom® installation, setup, and configuration activities; disable log files after your Gcom hardware and software are up and running.

Caution - To avoid filling your system disk drive with log file information, specify a maximum log file size to configure each log file to operate in a circular fashion.

Gcom_pcd Log File (pcd.log)
Contents Global events, such incoming calls, connections, dropped calls, and terminated sessions
Storage location /usr/spool/gcom
You control
  • If log file is enabled/disabled
  • File name
  • File storage location
  • Maximum file size
  • Level of detail
To enable Use the browser-based interface.
Default: Disabled
To configure Use the browser-based interface.
To access Use the browser-based interface.
Gcom_ssd Log File (ssd.log)
Contents Global events, such incoming calls, connections, dropped calls, and terminated sessions
Storage location /usr/spool/gcom
You control
  • If log file is enabled/disabled
  • File name
  • File storage location
  • Maximum file size
  • Level of detail
To enable Use the browser-based interface.
Default: Disabled
To configure Use the browser-based interface.
To access Use the browser-based interface.
SyncSockets® API Log File (gpi.log)
Contents TCP events in Gcom_ssd, such as incoming connections, outgoing connections, connection states, and connection requests
Storage location /usr/spool/gcom
You control
  • If log file is enabled/disabled
  • File name
  • File storage location
  • Maximum file size
To enable Use the browser-based interface.
Default: Disabled
To configure Use the browser-based interface.
To access Use the browser-based interface.
Legacy API Log Files
Contents Protocol-specific events in Gcom_ssd, such as incoming connections, outgoing connections, connection states, and connection requests
Storage location /usr/spool/gcom
You control
  • If log file is enabled/disabled
  • File name
  • Maximum file size
  • Level of detail
To enable Use the browser-based interface.
Default: Disabled
To configure Use the browser-based interface.
To access Use the browser-based interface.
System Log File (cmessages)
Contents CDI-, DLPI- and NPI-level protocol processing events, actions the Gcom STREAMS environment performs, and the logic for those actions
Storage location System messages file
You control
  • If log file is enabled/disabled
  • Level of detail
To enable Use the browser-based interface.
To configure Use the browser-based interface.
To access Use the browser-based interface.
Gcom_monitor Log File (logfile)
Contents Initialization and other events (such as link up/down) for each legacy protocol module.
Storage location /usr/spool/gcom
You control Nothing
To access Use the browser-based interface.

 		  

Click here for larger Solution Architecture diagram.

For more information...