Well, I have seen a similar problem, but not on any recent version of AIX.
Mine was back in the time that 4.1.5 was current.
The problem then was that AIX was making the application wait while it released
both the paging space on the disk as well as
the storage in memory when you did a free, and ipmap has a lot of stuff to free
when he finishes. The solution then was to
export an environment variable, which told AIX not to do that, BEFORE we
started the GUI.
You could try that. Stop all your GUIs, export NODISCLAIM=true , and then
issue netview from the same window. After
the map synchronizes, close it and see whether ipmap goes way quickly or not.
If it doesn't, then it is time to call
Support, because you'll need to run traces to find out what ipmap doing. From
what you posted, it looks like ipmap is not
the only one, either, which makes me think this is a system thing and not
really a NetView thing.
Tivoli (NetView for UNIX) L3 Support
Rob Napholz <tel1rxn@NJCMAIL.UPS.COM> on 10/11/99 02:44:41 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
cc: (bcc: James Shanks/Tivoli Systems)
Subject: closing the map + ipmap
Has anyone seen this problem ?
When closing the map(file exit) ipmap does not die.
ps -aef |grep tel1rxn
tel1rxn 26916 1 82 14:22:11 - 7:50 /usr/OV/bin/ipmap
WARNING: One or more processes are incorrectly parented.
PID PPID COMMAND
17174 1 collmap
26916 1 ipmap
29978 1 ipmap
30344 1 collmap
Run the following as root user to try to correct the problem.
If root or the users starts netview, netview will stop/kill ipmap
causing it to core dump ?
So why isnt ipmap stopping when the map is closed ?