Title: | Zap Technical Conference |
Notice: | ZAP Version 5.3 is available. See note 1.1 |
Moderator: | ZAPDEV::MACONI |
Created: | Mon Feb 24 1986 |
Last Modified: | Mon May 05 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 170 |
Total number of notes: | 492 |
I'm using ZAP V.5.0 on MVAX 3900 with VMS 5.4-2. The problem I have, is that ZAP$LOG_NODENAME.LOG file is growing continuously. After one day is about 10000 blocks, and this is causing disk space problems. What is recorded typically, is " %ZAP-W-NORULE no rule found for process XYZ". This is recorded hundred or thousands of times. How can I stop this completely unuseful logging ? Thanks for any kind of help. Ciao - Gianni
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
121.1 | You need a 'global' rule for the last rule | ZAPDEV::MACONI | The Doctor is In | Mon Oct 26 1992 13:19 | 21 |
It sounds like you have not placed a 'global' rule that applies to all processes in your exception database. The last rule in the exception database should always be in the form: NODE: * USERNAME: * UIC: [*,*] IMAGE NAME: * PROCESS CLASS: ALL TERMINAL NAME: * FROM: 00:00 UNTIL: 23:59 WARNING: Y IDLE LIMIT: <any integer or * for no limit> ACTION: STOP or LOG ... If, by default, you want to log people off, then specify an idle time limit and the STOP action. If by default you want to ignore people, then use the idle time limit * (none) [The action will never be used, so STOP or LOG are the same] Keith Maconi | |||||
121.2 | You are right | TRN02::MAINA | IT ALWAYS RAINS WHERE IT'S ALREADY WET..I'M SO DRY | Thu Oct 29 1992 03:33 | 5 |
Keith, you were right: a 'global' buffer rule was missing. Now it works fine. Thanks a lot Ciao - Gianni |