🚀 go-pugleaf

>>Once you have fixed it up, I beleive there is a way of setting up the audit
>>server so that the machine simply suspends anything which is waiting on the
>>audit server.
>
>A much more effective command which will prevent the problem from
>reoccuring is set audit/server=stop, preferably in the system startup
>procedure.

I found out how to keep the audit server from ever starting up in the
first place.  In the SYSMAN STARTUP database STARTUP$STARTUP_VMS, there
is a file called VMS$CONFIG-050_AUDIT_SERVER.COM.  Disable this file (on
all nodes, if you're in a cluster), and the audit server will never
start.  I think this was mentioned somewhere in the release notes for
the version of VMS in which the audit server first appeared.  I don't
remember where I found it, but it is a handy thing to do.  You just need
to remember to do it every time you upgrade VMS (oops, I mean OpenVMS :-).

>I strongly object to a system being delivered with the default
>configuration one that will prevent the system from running when an otherwise
>easily correctable system management problem occurs.

I fully agree.  VMS should come with the audit server disabled in the
manner I described above.  It is a very simple matter to turn it on if
you need it.

                                ++Don Nash

The University of Texas System			Internet:  D.Nash@utexas.edu
Office of Telecommunication Services		BITNET:    DON@THENIC