[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:	POLYCENTER Console Manager
Notice:	Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:	CSC32::BUTTERWORTH

Created:	Thu Aug 06 1992
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1541
Total number of notes:	6564

143.0. "OpenVMS VAX PCM V1.1 eft2 problems " by MUNICH::KASER (get stoned - drink wet cement !!!) Tue Dec 07 1993 16:10

    I've installed PCM V1.1 eft2 on my VS4000-90, OpenVMS 6.0,
    and MOTIF v1.1 ( ! )
    
    if i try to edit config-file i get the following error
    
    $ console c3
    ! a c3 window comes up and in the dcl window it says:
    Check and set linerr
    Execute :
    CONSOLE EVENTLIST -
         /NODE=0 -
         /SERVER=0 -
         /SCREEN=0 -
         /TRANSPORT=LOCAL
    C3 Message log file: sys$sysdevice:[kaser]cm_c3_KASER_output.log
    Console Manager - Cannot get shared memory pointer
    Check and set linerr
    Check and set linerr
    Check and set linerr
    Check and set linerr 	! this line is repeated 
    .
    .
    .
    
    What's wrong with my system ?
    Any hints ?
    
    btw.: i think, it's not a good implementation if the console-manager
    	  can only be installed from the system account and any
    	  creation/modification of the config-files.
    	  ( it took me a long time to figure that out - with 'all'		
    	  privileges set for my account !!! - Superuser ? )
    	  INSPECT doesn't allow to have a privileged account (i.e:
    	  SYSTEM ) to be shared by many peoples !
    
    many thanks
    Manfred

T.R	Title	User	Personal Name	Date	Lines
143.1	RTFM	OPG::PHILIP	And through the square window...	`Tue Dec 07 1993 18:42`	60
	Hi, >> $ console c3 >> ! a c3 window comes up and in the dcl window it says: >> Check and set linerr >> Execute : >> CONSOLE EVENTLIST - >> /NODE=0 - >> /SERVER=0 - >> /SCREEN=0 - >> /TRANSPORT=LOCAL >> C3 Message log file: sys$sysdevice:[kaser]cm_c3_KASER_output.log >> Console Manager - Cannot get shared memory pointer >> Check and set linerr >> Check and set linerr >> Check and set linerr >> Check and set linerr ! this line is repeated >> . >> . >> . >> >> What's wrong with my system ? >> Any hints ? Nothing is wrong with your system, these are debug messages we accidentally left in the code! However, the cannot get shared memory pointer line and the repeat of the check and set linerr wouyld indicate to me that you have started the C3 awithout having first starting the console controller daemon. The repeated check and set message indicates that the C3 is periodically trying to connect to the controller daemon. >> btw.: i think, it's not a good implementation if the console-manager >> can only be installed from the system account and any >> creation/modification of the config-files. >> ( it took me a long time to figure that out - with 'all' >> privileges set for my account !!! - Superuser ? ) >> INSPECT doesn't allow to have a privileged account (i.e: >> SYSTEM ) to be shared by many peoples ! >> >> many thanks >> Manfred >> We have had this feedback before, it is not going to change, the reason we do this is because we have our own security mechanism built into the database in order to allow or disallow access to consoles, the only way we could guarantee that the installation was successful (because the install edits the database) without circumventing the security mechanism was to only allow installation from the SYSTEM account. We could reverse this and allow anybody access to everything, however we felt that it was better for us to make the product secure "out of the box". This is also documented (or should be!) there are other considerations to make before and after installation which are documented also (especiallu on ULTRIX and OSF) so not reading the documentation first could have caused you a lot more problems than you already had. Cheers, Phil
143.2		CSC32::BUTTERWORTH		`Wed Dec 08 1993 21:25`	6
	Re -2. Bear in mind that you must only INSTALL the product from the SYSTEM account. Once you have installed the product you may add as many usernames as you wish and grant them the priviledge to modify the config database and reconfig the system.