Reverse Proxy routing file

Edit online

This topic describes the details and specifications of a Reverse Proxy routing file.

The default routing file for a Reverse Proxy server contains message log specifications similar to the specifications in Figure 1.

Figure 1. Sample Reverse Proxy routing file
FATAL:STDERR:-
ERROR:STDERR:-
WARNING:STDERR:-
#NOTICE:FILE.10.100:/var/pdweb/log/msg__notice_%ld.log
:644:ivmgr:ivmgr
#NOTICE_VERBOSE:FILE.10.100:/var/pdweb/log/msg__verbose_%ld.log
:644:ivmgr:ivmgr
By removing the number sign (#) from the NOTICE specification and stopping and then restarting the Reverse Proxy server, NOTICE messages are written to a set of 10 files. Assuming that the process ID of the Reverse Proxy server is 1017, the names of the 10 files would be: 
/var/pdweb/log/msg__notice_1017.log.1
/var/pdweb/log/msg__notice_1017.log.2
/var/pdweb/log/msg__notice_1017.log.3
/var/pdweb/log/msg__notice_1017.log.4
/var/pdweb/log/msg__notice_1017.log.5
/var/pdweb/log/msg__notice_1017.log.6
/var/pdweb/log/msg__notice_1017.log.7
/var/pdweb/log/msg__notice_1017.log.8
/var/pdweb/log/msg__notice_1017.log.9
/var/pdweb/log/msg__notice_1017.log.10

Message logging starts with the first file, /var/pdweb/log/msg__notice_1017.log.1. After 100 NOTICE messages are logged to that file, messages are written to the next file, /var/pdweb/log/msg__notice_1017.log.2. Message logging continues in this manner until 100 messages are written to the /var/pdweb/log/msg__notice_1017.log.10 file. At that point, the messages in the first file are deleted, and logging resumes again to the /var/pdweb/log/msg__notice_1017.log.1 file.