Well, all that means is that the cause is not really in the code but in the
system resources, somewhere. That's why I was suggesting the ulimits be
checked. For example, the default ulimit in AIX for the number of concurrent
processes which any one user can open is 40, and it is possible that you could
exceed that value in some cases, depending on what else you are doing, so then
the demand poll window wouldn't open, and then when some others finished, it
would. Do you see what I am driving at here? The problem could be process
limits, or available memory, or data stack, and so on. In Version 6.0 and 6.0.1
we have tried to reset the ulimits when the GUI is restarted to make this less
likely but hat will only be as effective as the system administrator has
allowed. If you aren't root, and you have a limit set for you by the root
administrator, then you cannot exceed that.
Every case of this sort of thing -- windows not opening, things not starting
from the GUI -- which we have investigated to date has been a resource issue of
this sort and that's why I gave the advice I did.
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
Torsten Syring <firstname.lastname@example.org> on 08/23/2000 03:53:11 PM
Please respond to IBM NetView Discussion <email@example.com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Re: Demand poll hangs
while waiting for an answer from the list,
the problem disapeared, and the demad poll works.
I could not try the ulimit command,
´m sitting at home.
Do You Yahoo!?
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Yahoo! Mail auf Ihrem Handy? - http://mobil.yahoo.de
NV-L List information and Archives: http://www.tkg.com/nv-l