27.3601%. (the highest on any one drive on the WRKDSKSTS screen is 72.2%). It has been suggested that it has something to do with reverse DNS Lookup and that I should tell the 400 what the addresses are. The problem with that is that they are dynamically assigned by the NT server and we are talking at least 50 users. Unless there is a way to generically tell the 400 about a range of addresses. -----Original Message----- From: Art Baker [SMTP:Art_Baker@baan.com] Sent: Tuesday, January 09, 2001 11:21 AM To: 'MIDRANGE-L@midrange.com' Subject: RE: Client Access Sessions taking forever to bring up Signon Scre en How full is your harddrive-wrksyssts. If your running over 80% it would be causing these long delays. Art -----Original Message----- From: Joe Giusto [mailto:JGiusto@patuxent.com] Sent: Tuesday, January 09, 2001 7:42 AM To: 'firstname.lastname@example.org' Subject: Client Access Sessions taking forever to bring up Signon Screen We are experiencing a very long delay when starting Client Access sessions. Sometimes it is taking 5 - 10 minutes to get to the signon screen. This usually occurs when there is an interactive job that is taking a large amount of resources. I have noticed that the job QTVDEVICE is running at Priority 50. My thought was to change this priority to 20 or below so that users will stop complaining about the delay for the signon screen. The question is, where is the best place to do this? I was thinking about changing the Class description, but have been unable to determine which one is being used, and I also do not what other jobs to use this priority (which would bring the system to it knees if there are other tasks that share this class/routing entry). Thank you very much for any suggestions that you can offer. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.