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

Conference ranger::pwosf

Title:PATHWORKS for OSF/1
Notice:see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX
Moderator:CPEEDY::LONG
Created:Thu Apr 22 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1874
Total number of notes:6870

1798.0. "lmx.dmn swapped out. how to prevent?" by RANGER::BACHUS::DHAENS () Thu Mar 27 1997 13:33

      A customer did a upgrade from pwosf V5.0 to V6.1eco2.
    
        As of that moment he has resource problems on the  server.
        Those are visible on the clients as:
        -DOS clients aren't validated at logon time
        -Server tools don't find a domain controller
        -printing problems
    
     Before the upgrade he never had problems.
     All problems seems to be related to the fact that the lmx.dmn process
     is swapped out. (and others also but this one has the highest
     visibility.)
     Can we prevent that process to be swappedd out?
     I already reniced this process, changed the pulse interval to
     60sec.
    
     Before the upgrade this server was used as a file and print server.
     Now because of the problems, the printers are moved to the BDC (a
     pwosf V5.0 server).
     What we see now is that from time to time a "CLASS DRIVER DOWN"
     message is seen on the BDC. This can be resolved with a  "net accounts
     /sync" on the PDC.
     It solves the problem but why?
    
     Is it possible that a Dec1000A 5/400 with 384MB of memory isn't
     enough for +-150 pc's.
    
     I hope to receive some explainations or hints,
      Geert Dhaens
T.RTitleUserPersonal
Name		DateLines