| Title: | VAX and Alpha VMS |
| Notice: | This is a new VMSnotes, please read note 2.1 |
| Moderator: | VAXAXP::BERNARDO |
| Created: | Wed Jan 22 1997 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 703 |
| Total number of notes: | 3722 |
If I have a common cluster queue file, do I have to have a common
cluster security audit file?
If the above is true , where is it documented?
If the above is not true, then I think I found a bug!
- Customer has a common queue file but separate audit files. He places
a security acl on a queue to observe succesful:manage. If I delete
the queue from the node where the queue manager is running, the info
is logged in the audit file. If I delete the queue from another
node, the event never makes it to the audit file. The problem
is specific to writing to the audit file, as any node will generate
an alarm and send it to an operators terminal.
comments???
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 364.1 | See VMScluster Manual... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Fri Mar 21 1997 13:53 | 8 |
An OpenVMS VMScluster is a single security domain -- this means one SYSUAF, one RIGHTSLIST, one NETPROXY, and one NET$PROXY. For the documentation, see the Master Index entry under "Security; VMScluster requires single domain". (This will point you to chapter five in the _VMScluster Systems for OpenVMS_ manual, in the documentation on preparing the shared environment.) | |||||
| 364.2 | AUSS::GARSON | DECcharity Program Office | Sun Mar 23 1997 21:47 | 24 | |
re .0
I couldn't reproduce this problem. I had a queue with the following ACE
(AUDIT=SECURITY, ACCESS=MANAGE+SUCCESS)
and on deleting the queue from a node where the queue manager does not
reside, the audit file on the node where the queue manager does reside
gained an "object deletion" event for the queue in question. No event
was generated on the node where the function was requested.
[The event was generated by the queue manager and the source PID
identifies the original requesting process on the non-queue manager
node.]
I see some surprise value here in a number of areas but nothing too
worrying.
What version of VMS is involved?
If you can reproduce this, please escalate formally with a log showing
what commands were entered (e.g. ANAL/AUDIT) and on what machine and
showing such things as SHOW QUEUE/FULL and (on both nodes) SHOW AUDIT
and an indication of where the queue manager is running.
| |||||