RE: nam usage

["Jeff Donahoo" <Jeff_Donahoo@baylor.edu>]

I have noticed this behavior as well under Linux, and the users do have
their own home directories (mounted over NFS).

Here's a hack we use:


     1. Go to the file anim-ctrl.tcl in the nam-1.0a7/tcl directory.
     2. Jump to function remote-create-animator
     3. Comment out the whole if/else statement
     4. Insert the following before the commented if/else statement:

     puts -nonewline "Cannot connect to existing nam instance. "
     puts "Starting a new one..."
     $self local-create-animator $trace_file [join $args]

     You may notice that these are the lines in the "if" part of the if/else
statement.

     5. In directory nam-1.0a7, type make. This should recompile NAM so that
every time
     you run it a NEW NAM CONSOLE is created.

This creates a new console each time you run nam, but it avoids the problem
of multiple users.  Anyone have any better suggestions?  Perhaps the problem
has been fixed.

Jeff

> Nam communicates with a "server" on a per-user basis. So as long as those
> users have their own unique home directories, they should not see this
> phenomenon.
>
> - Haobo
>
> On Tue, 25 Jan 2000, Fusun Inanc wrote:
>
> > Hi everyone,
> >
> > I have another question. In my Sun Solaris 2.7 unix system
> there are three
> > users using ns2.
> >
> > I have just realised that if one user uses nam in his/her
> simulation first and
> > if the other user wants to use it at that time, the second
> user's nam window
> > pops up on the first user's screen.
> >
> > I copied the nam executable files in different directories for
> each user but
> > the problem still exist.
> >
> > I think if nam is running as a process on the unix server, it cannot
> > run another process.. Is that true? Or is there something that I can do?
> >
> > Thanks for your kind help.
> >
> > Fusun Inanc
> >
> >
>
>