Conference azur::mcc

5909.0. "Creating domains with user different from root" by LISVAX::KALENGA () Mon Mar 14 1994 10:32

    Hello, I am having an unusual situation at one of my customers (this
    has never happened before at any other customer). I am using DECmcc/BMS
    for ULTRIX V1.3.
    
      When I start the Iconic map with a user different from root (for
    example user mcc, which is part of the group mccuser), the map 
    displays. When I then try to create a new Domain, for instance:
    
       Domain name: isep
       Owner Id: mcc
       Directory: /usr/users/mcc
    
    I receive the following messages:
    
       The requested operation cannot be completed.
       MCC unhandled service reply.
       %MCC-E-IO-ERROR, error was returned by I/O facility
    
    When I try to open an existing domain (created with the user root),
    I receive the following messages:
    
       The MIR could not be initialized
       Can't open master repository table: permission denied.
    
    As stated in the manuals, I have set the group-id of /var/mcc/* and
    /var/mcc to mccuser, and mcc is a user of the group mccuser. 
    The only "non-standard" issue, is that users, groups, hosts, etc. are
    defined with BIND, and the BIND server is another ULTRIX host. But I
    think that this shouldn't be a problem.
    
    When starting the iconic map as user root, I can create and open
    domains without any problem, but this isn't obviously a good solution
    for the customer.
    
    I have reinstalled DECmcc on the system, and the same problem happens
    again. I have tried to reproduce the problem here at the office, but
    everything works alright when starting the iconic-map with a user that
    is part of an mccuser group (with /var/mcc/* & /var/mcc group-id set to
    mccuser).
    
    Any hints?
    
    Thank you and regards,
    Kalenga d'Almeida
    SNOS/DC - Lisbon
    
    

  
  Kalenga,

  This *has* to be a protection problem !

  Could, try stopping all mcc processes, via kill or shutdown and then
  change the protection of the /var/mcc directory with :

	chmod -R 777 /var/mcc

  and try again.

  This will deprotect completely your /var/mcc files, thus 'solving'
  potentially all the protections problems.

  Regards.

  Pierre.