Conference csc32::consolemanager

    Marc,
    
       Here's where you can pick up a copy of the latest documentation
    (on a VMS system).
    
    IOSG::disk$swapper1:[knott$proj.eccm.mgt_guide]console_manager_mg_profile.ps
    
    The documentation write is HOLLIE::karen Campbell and I'm sure she
    would love to get some feedback from you. She's located in the UK.
    
    Now, about how the events and scan,s etc play together. Basically, once
    you understand it, it's easy. A Scan profile (i.e. record) is nothing
    more than a group of events. It may also contain the names of other
    scan's as well. Think of it as having a binary tree structure where
    all the leaves are events. There can only be one definition at the top
    and that is the name that you put into the system record definition.
    CM decomposes this tree and ends up with a list of events that it
    must watch for. The whole rationale is for ease of use. Imagine the
    work you would have to go through if you had to list each event 
    seperately for each system you added. If you had 200, it would be
    a nightmare to maintain.
    
    In your case, youhave a scan profile called UNIX. This in turn has 5 
    other scan profiles listed in the tree (_SCAN$UNIX_001, _SCAN$UNIX_002,
    etc). The scan _SCAN$UNIX_001 contains the list of events. Now, to add
    the bad SU attempt, you first need to create an event. Using the
    command line version (cm -E), it might go something like this:
    
    CM EDIT> add event
    Event name: BADSU
    Class  (DEFAULT):
    Information: Bad SU attempt
    Text: BADSU:
    Start [0-999] (0):
    Count [1-1000] (1):
    Priority [1=Critical, 2=Maj, 3=Min,4=Warn, 5=Clear, 6=Indet] (5): 3
    
    OK to add? [Y/N] (Y):
    
    Next, you would want to add the event into the scan profile. You could
    do this either by creating another scan profile or simple and add it to
    the  top level UNIX scan profile or add the event directly to the 
    UNIS profile. For simplicity, we'll add it to the UNIX scan record.
    It would look like this:
    
    CM EDIT> modify scan
    Scan name: UNIX
    Information (UNIX System V Scan Profile):
    Enter new event names to add. (? = list)
      Add Event (CR=end): BADSU
      Add Event (CR=end):
    Enter Subscans names to remove. (? = list)
      Remove Subscan (CR=end):
    Enter new Subscan names to add. (? = list)
      Add subscan (CR=end):
    
    
    OK to modify? [Y/N]  (Y):
    
    Event Name      = BADSU
        Information =
        Class       = DEFAULT
        Text        = BADSU:
        Text string = Literal (exact pattern match)
        Start       = 0
        Count       = 1
        Priority    = Minor
    
    CM_EDIT> exit
    
    You'll have to shut down CM to get the daemon to re-read the database
    as I'm not sure if the reconfiguration command is fully functional.
    
    Hope this helps,
    
    Dave

Is there any VMS CM doc available ?

I already copied the lastest doc you mentionned in -1.

>You'll have to shut down CM to get the daemon to re-read the database
>as I'm not sure if the reconfiguration command is fully functional.
 
The documentation says 'cm -r' in V1.0 kill the daemons
and restart it. Next version will make a kill -HUP.

Actually, cm -r generates a segmentation fault and you
have to manually kill the processes and restart using
cm_startup.

Thanks for the previous inputs.
Btw, I tried to create my own event, put it in in scan
profile and tried to use it ... but without success.
Will continue to try ... but really without a good
doc, it is painfull.

Marc.  

Still doesn't work ... don't know why ?

Is this correct :

I create 2 events (using the x config menu)

Name :			Boot_promt
Class:
Information:
Text to Watch for:	>>
Watch Type text:	Literal
Event Priority:		Critical
Event Context Start:	0
Event Context Count:	1

Name:			Login_incorrect
Class:
Information:
Text to Watch for:	Login incorrect
Watch Type text:	Literal
Event Priority:		Major
Event Context Start:	0
Event Context Count:	1

I create a scan profile :

Name:			BRO
Information:
Events:			Boot_prompt
			Login_incorrect
Sub_Scans:

My question is now : How to make this work ?

Marc.

    Have you ammended the scan you created , BRO, into the scan that the
    system is using? If it was the UNIX scan, you'll have to modify that
    one by adding in the BRO scan you've just created. It should look like
    the following:
    
      
                                    UNIX  <- top level scan definition
                                     |
                          ---------------------                 
                          |                   |
 Other definitions ->  _SCAN$UNIX            BRO   <- Your new definition
                          |
                -------------------  
                |    |    |   |   |
                Various other profiles
    
    

Thanks but I finally succeeded by adding my 2 events
to the _SCAN$UNIX profile.

I just tried what you said and finally understood.

Indeed, when you understand once how it works,
it's very easy ... Begin to like it ...


Thanks again for your patience regarding a novice.

Marc.

    Hi Marc,
    
    Let me apologise for the lack of information in the documentation.
    The versions you have are very early drafts and we are constantly
    adding new information.  Feel free to copy the latest version of
    the Users' Guide from the located Dave pointed out earlier...I think
    you'll find much more information in it than before.
    
    Also, please bear with us.  We're writing the information as fast
    as we can.  Unfortunately, the event notification chapter has
    not been written fully, but we are getting there slowly.
    
    If you have any comments or requests for information to go into
    the book, then please mail me on wessex::karen.  It's the only
    way we'll improve our documentation if real users give us some
    real feedback.
    
    Thanks and regards,
    
    Karen
                                                          

Karen,

I know we are living in difficult times and that every
body is doing his best. (really)

My remark concerning the doc is intended to stress the
product manager that if he wants to succeed with CM
in the Unix community, he has to put the documentation
writing at a high priority. 

Let me suggest you one thing in the doc. Put on one
page a draw with the relations of all CM entities
(clients, scan_profile, event, watch, ...)
The goal is to give with one page a fast way to under-
stand how all CM things fit together.

Also, let's document all the UNIX events which come
by default with CM.
(btw, 'System V' should be replaced asap by 'Unix')

Thanks and regards,
Marc.

    Hi Marc
    
    Thanks for your comments.  I like the idea of an overview of all
    the CM componenets and will include it in the book.
    
    Regards,
    
    Karen

    The Field Test versions of the Installation Guide and the Users' Guide
    are now available.  They do differ quite a lot from the versions 
    you have.
    
    The Installation Guide is in :
    
    iosg::disk$swapper1:[knott$proj.eccm.inst_guide]ft_cm_install.ps
    
    The Users' Guide is in:
    
    iosg::disk$swapper1:[knott$proj.eccm.mgt_guide]ft_cm_users.ps
    
    IN ADDITION, there is a reference card for users of CM (as opposesd to
    those setting it up and managing it on the host system).  If you'd
    like a copy of the card, please let me know and I will send you one
    through the internal mail as it isn't available as an electronic
    file.
    
    As before, if you have any comments on any part of the
    documentation, including the gui help text and cm(1) reference page,
    please let me know.  My DTN fax number is 830 3690 and my mail
    address is hollie::karen.
    
    Thanks and regards,
    
    Karen
              

    r.10 May I know what do you mean by Reference Card?

send me the card please (Marc Sybertz @BRO)

Thanks for your efforts,
Marc.

    The reference card lists all the commands a user of CM would need
    to know, as opposed to someone who was setting up and managing
    CM on the host.  It's a gatefold card with six panels.
    
    It's intended as quick reference and to give you an idea of the
    commands you need to use for certain tasks just at a glance.  It
    doesn't go into detail.  There is additional information
    in the users' guide and cm(1) reference page to supplement it.
    
    Hope this helps...
    
    Karen
    
    PS Marc - a copy is on its way...

    So, those of you who have used the books and the card, do you
    have anything to say?  
    
    I'd be interested to hear if you have...everyone is being so quiet.
    
    Thanks and regards,
    
    Karen 

Karen,

Speaking for myself, it is not because the product is
not interesting ... but I just don't have time to
continue to test it for the moment.
Also, I'm waiting to have some lines available in our
computer room very soon to connect internal production
machines.

You will hear me soon I hope.

Marc.

    Look forward to hearing from you Marc!
    
    Karen