| Dave,
Some answers...
>- Does not shut down when shutting down CM. CM will not come up id ENS is
> running.
>
This will occur if you do not have the Console Manager shutdown event
defined in the database, can you check that it is there?
>- Not all events are being detected. Apparently there is a hard-coded
> limit of events. I tested the 'UNIX' scan profile. Not all the events
> were being detected.
There is no hard-coded limit, can you describe more fully the circumstances
upon which the events were not detected, have you tried sending a file with
all the events in question to the console to see if they are all picked up?
>- If an action 'command' is not defined properly, how can I debug it?
> In other words, I think I have what is a properly defined action and
> watch records. However, nothing ever happens. Is there some type
> of log file present indicating what went wrong?
At the moment, no, we have disabled the logging facility, as we had some
problems with it, it will be reenabled soon.
>- Should the database come loaded with some defined action routines?
> It seems like this would be easy to do.
Yep, and the actions should have been loaded for you via the template
import file (/usr/kits/DCR100/templates/cm_config.PORT) I will take a
look at this.
Cheers,
Phil
|
| Phil,
Here's some additional re -.1:
I don't have the name of the CM shutdown event, so I don't know if I
have it or not. IFT2 was an upgrade for me. Perhaps IFT1 did not have
all of the action routine definitions nor the shutdown event defined.
I can delete the database and re-install th kit to see if that helps.
The only bummer is that I cannot restart the CM daemon if ENS is
running. I must first kill off the ENS process before I issue a
cm_startup command.
Regarding the event limit: It would appear that it is only picking up
the first event and that's it. It may have something to do with the
fact the action routine is not getting kicked off properly.
I'll prod around more little more today.
Dave
|