>are you going to fix it?
>At 11:59 AM 5/1/97 -0700, John G. Thompson wrote:
>>Yes, I've seen it.
>>
>>Accounting data is considered critical data and it is kept in the machine
>>until either there is an ack from an accounting server or, as you have
>>seen, the ComOS 'wigs out'.
There is a fix.... Define a secondary accounting server to take the
data when the primary bombs out. set accounting 2 xxx.xxx.xxx.xxx
This will prevent the ComOS from "wigging out" due to lack of memory.
Same reason you have a secondary DNS server and a secondary RADIUS
authentication server. If memory is running out because people are
logging on and off and the authentication server is running and accounting
is not, then maybe your authentication server should be your backup
accounting server. If both authentication and accounting are down at
the same time, this issue should be moot and never come up unless you
have so many people that logoffs are a problem or you are running low
on PM memory. If its the too many people/term servers, then maybe you
need to split the term servers up into groups each with their own
servers and backup servers. If its too little memory, the answer is
obvious. I don't see a graceful solution short of trashing accounting
data when memory becomes full, but the PM does not seem to devote
any time to checking available memory.