Hello Kashif,
The dispsub process *should* go away when you shut down the NetView gui.
The only time I have seen it get left behind (after which it may begin to
loop and take up CPU, a problem we are looking at) is if NetView was
shutdown improperly. e.g. stopping the daemons without first stopping all
of the guis. If it's left behind from a previous shutdown, it will
disconnect from ovw and a new one will start when NetView is restarted.
There should only be one.
If you are not using the dispsub function at all, I recommend you disable
its startup by editing
/usr/OV/registration/C/dispsub
and removing the '-Initial' flag from the command startup line.
At 02:20 PM 07/20/1999 -0400, you wrote:
>Netview 5.1.1 on Solaris 2.6.
>
>I can see multiple instances of dispsub process started on my Netview
>server on different dates. I understand that this process should only
>start when I am trying to look at Netview submap from the TEC console.
>Something that I never do.
>Question: Does dispsub also start if I use the Tivoli console to start
>a Netview user interface? The command used in that case is
> nv6000_smit applstart -map 'Main' -mode '-ro'
>why I ask, because the userid dispsub seems to have multiple instances
>running from, starts netview with this command (wanted to open a
>read-only NV map only actually). The other userid that uses the netview
>script to start GUI also has an instance of dispsub running from it.
>Why?
>
>Dispsub doesn't seem to be cleaning itself up after the GUI is brought
>down. how can I address that..??
>
>Thanks
>Kashif
>_________________________________________________________
>Do You Yahoo!?
>Get your free @yahoo.com address at http://mail.yahoo.com
>
Scott Donohoo
Tivoli NetView for UNIX/NT L2 Support
|