[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

727.0. "PCM 1.6 FT Protection-problem" by 51651::SJOBERG (Bernt Sjoberg @GOO) Fri May 12 1995 14:36


	Hello !

	I have a customer who had VERY big problem with PCM 1.5 ( The 
	wellknown RWAST bug...). I gave him the 1.6 FT kit and so far 
	he is satisfied with the 1.6 release, ( he is aware of that this is
	field test ) . Now he have some minor problem and he asked me 
	the following...

" Hi 

I have run in to a minor (?) problem with console manager 1.6 FT. I have some
console-ports for routers and other kind of communication equipment which is
included in a separate group within PCM and that group is only accessible for
the communications people. The communications people is ordinary, unprivileged
users in VMS (PCM runs on an alpha 3k800s by the way) and this configuration
worked with version 1.5. What happens in 1.6 FT is that when they start C3 the
basemap shows all groups (including those who they have no access to) but
systems are only shown in the communications group which is the only group
that they have access to. All systems are gray (no connection) and when they
try to connect to a system they get a message "PCM is not running", PCM is
indeed running. I assumed that this is some kind of protection-problem, so I
gave the communications people full system privileges. What happens now when
they bring up C3 is that they can now only see the communications group and
the system in that group and connections works just fine."
-----------------

	Is this a known problem ? / Bernt
  



T.RTitleUserPersonal
Name
DateLines
727.1PBUNIX::pgbAnd through the square window...Fri May 12 1995 14:5916
Bernt,

  Have you rebooted since the install?

  We have changed the way the software works, we no longer install the 
  images with privs, consequently, we need to grant write access to the 
  PCM logical name table, now, this protection doesnt get changed on 
  the name table yet at install time (We are currently fixing this for the 
  next kit).

  So, either reboot, or, shut everything down, delete the 
  CONSOLE$LOGICAL_NAMES table and then restart PCM.

Cheers,
Phil