[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 | 
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit | 
| Moderator: | STAR::VATNE | 
|  | 
| Created: | Mon Oct 30 1989 | 
| Last Modified: | Mon Dec 31 1990 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 3726 | 
| Total number of notes: | 19516 | 
838.0. "DECwindows session manager hangs on LOGIN" by 29576::CALDRELLO () Wed May 24 1989 11:51
    I have a VAXstation 3520 satellite in a VMS 5.1-1 LAVC environment.
    A certain user tries to login and the session hangs.  The menu
    bar comes up then everything freezes.  This does not happen with the
    SYSTEM account, and several other NON-privileged user accounts.
    
    This user's DECW$SM.LOG contains the following:
    
    %SET-I-NEWLIMS, new working set: limit=201, quota=201, extent=16400
    %DCL-W-ACTIMAGE, error activating image SMGSHR
    CLI-I-IMGNAME, image file
    VENUS$DUA0:[SYS10.SYSCOMMON][SYSLIB]SMGSHR.EXE
    %SYSTEM-F-INSFWSL, insufficient working set limit
    
    SYSGEN WSMAX is 16400
    
    The UAF record for the user has:
    
    WSDEF = 2000
    WSQUO = 30,000
    WSEXTENT = 30,000
    
    I renamed the user's LOGIN.COM to something else so it wouldn't
    execute, and the same thing happened.
    
    Any ideas?
    
    Lou Caldrello
    
| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 838.1 | DECW$LOGIN, not LOGIN | 34858::SOCHA | Out in the Field | Wed May 24 1989 12:01 | 5 | 
|  |     Check to see what is in the users DECW$LOGIN.COM file.  This is
    run during DECwindows login.
    
    Kevin
 | 
| 838.2 | No DECW$LOGIN.COM | 29576::CALDRELLO |  | Wed May 24 1989 13:04 | 12 | 
|  |     Kevin,
    
    There is no DECW$LOGIN.COM in the user's directory.  There is the
    DECW$SYLOGIN.COM in SYS$MANAGER, that has one command:
    
    $set working_set/quota=200
    
    ??
    
    Lou
    
 | 
| 838.3 | fixed the problem | 29576::CALDRELLO |  | Thu May 25 1989 12:16 | 10 | 
|  |     In case anyone was wondering, we fixed the problem.
    
    Turns out some of the Working Set quotas for this one user's account
    were set too high!?
    
    We changed WSQUO from 30,000 to 4096, and WSEXTENT from 30,000 to
    8192.  The user logged in and everything worked!
    
    Lou
 |