Closed Bug 43125 Opened 24 years ago Closed 24 years ago

No more DecWindow terminals after starting Mozilla

Categories

(Core Graveyard :: Tracking, defect, P3)

DEC
OpenVMS

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: munk, Assigned: colin)

Details

OS: Vms 7.2-1 with mandatory updates
system: PWS500au
Mozilla M16

After running Mozilla M16 it is no longer possible to open new DecWindow 
terminal sessions ('FTA' devices). Normal terminal sessions (telnet etc.) are 
still possible. Removing the installed components from memory (install.com 
remove), or restarting X-Windows will not help, only a reboot. Other X-Windows 
applications do not seem to be affected.
qawanted -- need someone with OpenVMS...

reporter: please retest this bug with a brand new M17 nightly build and post 
the results here...
Keywords: qawanted
Whiteboard: [need update][6/27]
Assigning to Asa to move along.  Not sure who Dec folks are in the eng dev and 
QA net community.
Assignee: chofmann → asa
QA Contact: leger → asa
colin it the main OpenVMS dude.
Assignee: asa → colin
How are you trying to start the DECterms? CREATE/TERM or CREATE/TERM/DETACH??

Can you post the account quotas for the account you are using to run Mozilla 
from (whatever account name you used when logging in to DECwindows).
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Some additional information:

I was trying to start the DECterm from the X-Windows desktop, just using the 
GUI.

these are my quotas etc.:

Maxjobs:         0  Fillm:       300  Bytlm:        64000
Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
Maxdetach:       0  BIOlm:       150  JTquota:       4096
Prclm:           8  DIOlm:       150  WSdef:         2000
Prio:            4  ASTlm:       250  WSquo:         4000
Queprio:         4  TQElm:        10  WSextent:     16384
CPU:        (none)  Enqlm:      2000  Pgflquo:     200000
Authorized Privileges: 
  ACNT         ALLSPOOL     ALTPRI       AUDIT        BUGCHK       BYPASS
  CMEXEC       CMKRNL       DIAGNOSE     DOWNGRADE    EXQUOTA      GROUP
  GRPNAM       GRPPRV       IMPERSONATE  IMPORT       LOG_IO       MOUNT
  NETMBX       OPER         PFNMAP       PHY_IO       PRMCEB       PRMGBL
  PRMMBX       PSWAPM       READALL      SECURITY     SETPRV       SHARE
  SHMEM        SYSGBL       SYSLCK       SYSNAM       SYSPRV       TMPMBX
  UPGRADE      VOLPRO       WORLD
Default Privileges: 
  ACNT         ALLSPOOL     ALTPRI       AUDIT        BUGCHK       BYPASS
  CMEXEC       CMKRNL       DIAGNOSE     DOWNGRADE    EXQUOTA      GROUP
  GRPNAM       GRPPRV       IMPERSONATE  IMPORT       LOG_IO       MOUNT
  NETMBX       OPER         PFNMAP       PHY_IO       PRMCEB       PRMGBL
  PRMMBX       PSWAPM       READALL      SECURITY     SETPRV       SHARE
  SHMEM        SYSGBL       SYSLCK       SYSNAM       SYSPRV       TMPMBX
  UPGRADE      VOLPRO       WORLD

I will try the M17 as soon as I can get it from the usual Compaq download site. 
I suppose that is the only place I can get it ?
Do you get the same failure if you try a CREATE/TERM/DETACH?

Can you look in DECW log files in your SYS$LOGIN to see if there are any 
messages?

Is your DECterm controller still running (do you have a process named 
DECW$TE_xxxx)?

Don't worry about M17. Nightlies aren't available for OpenVMS, and besides, this 
is a configuration problem, not a Mozilla bug.
I tried create /term /detach and got the error message that the MAXBOBMEM limit 
was exceeded. Luckily it is a dynamic sysgen parameter, so I could change it on 
the running system from the default 1600 pagelets to 3200 pagelets. And bingo, 
all was fine again. no more problems.

I had some other problems too with Mozilla, but before reporting them I will try 
it with this setting and see what happens.

I suppose the MAXBOBMEM issue is something for the release notes, so I will 
leave it to the persons responsible for the VMS port to take the actions they 
find appropriate, and to close the problem.

Thanks for all your help,

Regards,

Dirk Munk    
Glad to hear that fixed the DECterm problem. I'll get something added to the 
OpenVMS release notes to cover this. 

If you see any further problems, please enter them as separate reports.

Thanks,

Colin.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Whiteboard: [need update][6/27]
Reported confirmed to me via mail that all the other problems he was seeing 
disappeared when he fixed MAXBOBMEM. Marking this as verified.
Status: RESOLVED → VERIFIED
Keywords: qawanted
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.