on 06-30-2009 6:03 AM
Hello,
We have the following parameters set
rsau/max_diskspace/local 20M
rsau/max_diskspace/per_day 0
rsau/max_diskspace/per_file 0
If I look in the DynamicConfiguration tab, it shows
Maximum File Size 100,000 MB
This seems a little crazy. Does anyone have any idea how the Max File Size got to be displayed so large?
Kind regards,
Peter
Hi Peter
rsau/max_diskspace_local or rsau/max_diskspace/local (depending on your SAP version) specifies the maximum length of the audit log by default is set to 1000000 bytes but it can be set much larger than that so I think you shoulc check tha current value of the parameter.
Regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Refer to SAP Note : 909734 - SecAudit: Parameter rsau/max_diskspace/local too small
-
As of kernel patch 2113 (4.6D) or 88 (6.40), the system requires a minimum size of 1 megabyte (1048576) for 4.6D, and a minimum size of 10 megabytes (10485760) for 6.40. As of kernel patch 134 (6.40), rsau/max_diskspace/local requires a minimum of 100 megabyte.
-
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually, I just checked at the OS level after activing the trace and logging in a few times.
The "Current File Size" shows as 10,156, but at the OS I can see that the size is only 10400 bytes.
Looks like the display is out of whack
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.