| Summary | This article outlines the GIOP Snoop log file management enhancement introduced in Orbix 6.3.5 hotfix 07 (Orbix 6.3.5.07). |
|---|---|
| Article Number | 36191 |
| Environment | Orbix 6.3.5 hotfix 07 All supported Operating Systems |
| Question/Problem Description | GIOP snoop log file management enhancement How does the GIOP Snoop log file management work? |
| Clarifying Information | The GIOP Snoop log file management enhancement is basically the GIOP Snoop equivalent of the Event Log log file management feature introduced in Orbix 6.3.5 hotfix 06 (Orbix 6.3.5.06). |
| Error Message | |
| Defect/Enhancement Number | ORB-2134 |
| Cause | |
| Resolution | GIOP Snoop File Management Currently existing is the following configuration variable:
This rolls the file on a date schedule, so a new day means a new file.
The following new variables have been introduced:
Setting the above configuration value string to "size" will instead roll the file when it reaches a certain size limit
If the above configuration value is set to "date", the filename will follow existing convention: /var/adm/giop_snoop.log.02172012 /var/adm/giop_snoop.log.02182012 /var/adm/giop_snoop.log.02192012 If strategy is set to "size", filename will follow this new convention: /var/adm/giop_snoop.log.2012.02.17.15.03.15 /var/adm/giop_snoop.log.2012.02.17.22.55.47 /var/adm/giop_snoop.log.2012.02.18.03.14.05
This is the size in Megabytes that the log file will grow to before it gets rolled.
When this is set to n, the (n 1)th log file and all older log files (if any exist) will be compressed.
When this is set to 0, no log files will be compressed.
When this is set to n, the (n 1)th log file and all older log files (if any exist) will be deleted.
When this is set to 0, no log files will be deleted. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 14 November 2012 |
|---|---|
| Last Modified: | 12 February 2013 |
| Last Published: | 14 November 2012 |
| First Published date: | 14 November 2012 |
#Orbix
#KnowledgeDocs
