[AG-TECH] 2 intstances vic.exe

[Sabihuddin, Siraj]

I had the same problem when I tried using both the video consumer and
producer services...each service starts up its own instance of vic.  Instead
try using only the Video service "VideoService.zip" that comes with AG 2.2 -
this version should implement both the consumer and producer in one vic
instance.

Siraj
Student Programmer
Information Security Group, Institute for Information Technology
National Research Council (NRC), Ottawa, Canada
Email: Siraj.Sabihuddin at nrc-cnrc.gc.ca, 
WWW - NRC: http://iit-iti.nrc-cnrc.gc.ca 


> -----Original Message-----
> From: owner-ag-tech at mcs.anl.gov [mailto:owner-ag-tech at mcs.anl.gov]On
> Behalf Of Mike Elmore
> Sent: Friday, June 04, 2004 1:10 PM
> Cc: ag-tech at mcs.anl.gov
> Subject: [AG-TECH] 2 intstances vic.exe
> 
> 
> Hello,
> I have installed 2.2 on a laptop with xp and I am able to go 
> into the rooms.  I
> still haven't verified the audio.  When I started the venue 
> client (after two
> installs) I had video consumer installed in the node.  In 
> order to send my video
> I had to add video producer or video service to the available 
> services.  They
> appeared to function identically.  Now, I have two instances 
> of vic.exe running
> and two windows.  1)video and 2)a window with the room name.  
> The problem is that
> when I go into a room with a lot of videos, my cpu usage is 
> always at or near
> 100%, which makes everything take what seems like forever 
> when I change rooms
> etc,.  I don't remember this happening in 2.1.2  All I had to 
> do was select the
> video and select transmit to transmit my video.
> Thanks,
> Mike
> 
> 
> Michael Miller wrote:
> 
> > Would this apply to linux as well?
> >
> > MYK
> >
> > At 11:35 AM 6/2/2004, you wrote:
> > >At 10:45 AM 6/2/2004, Frank Sweetser wrote:
> > >>I just removed AG 2.1.2 from my laptop, and then 
> installed AG 2.2.  I've had
> > >>two issues so far
> > >>
> > >>         - The GLOBUS_HOSTNAME environmental variable was 
> still set to an
> > >>           old hostname.  Previously, when the venue 
> client started up, it
> > >>           would detect that GLOBUS_HOSTNAME wasn't set 
> to a hostname that
> > >>           was valid for one of the interfaces and bring 
> up a dialoge box
> > >>           to properly set it.  Now, though, various bits 
> and pieces just
> > >>           try to talk to a hostname that doesn't map to 
> any of the local
> > >>           interfaces, and isn't even up.
> > >
> > >The new code detects the hostname to be used, *unless* 
> GLOBUS_HOSTNAME is
> > >set.  The philosophy is that if the autodetection does not 
> work properly,
> > >we're probably in an environment where the autodetection 
> couldn't work
> > >(for instance, we're behind a NAT).
> > >
> > >Unfortunately, this leads us to the problem you're seeing. 
> Probably the
> > >best thing to do is to go to the environment control panel 
> and remove the
> > >definition of GLOBUS_HOSTNAME to allow the autodetection 
> to go ahead.
> > >
> > >--bob
> >
> > Thanx,
> >
> > Michael Miller
> > System Engineer
> > Visualization Technology Support
> > Computing and Data Management
> > National Center for Supercomputing Applications
> > University of Illinois - UC
> > 217-649-0747
> >
> > "If you're clear in your vision and trust the people in 
> your team with
> > clear objectives, they will invariably do their best to 
> achieve everything
> > desired, and usually deliver everything you could have 
> hoped for and even
> > more." -Paul Debevec
>