> 
>    That's my delpeer.pl file:
> 
> # cat /usr/local/TAUSRC/Local/ToolBox/delpeer.pl
> #!/usr/bin/perl -w
> 
> use File::Temp qw/ tempfile tempdir /;
> 
> ($fh, $filename) = tempfile('/tmp/delpeerXXXXX',UNLINK => 1);
> 
> print $fh "delete type: NSR peer information; name: $ARGV[0]";
> 
> print $fh ("\nquit\n");
> 
> close($fh);
> 
> sleep 2;
> 
> system ("nsradmin -i $filename -p nsrexec -s legato");
> 
> sleep 2;
> 
> 
>    Goes well with
> 
>   grep 'There is already' /nsr/logs/daemon.log | awk '{print $15}' | 
> sort | uniq


Thanks but that is not the message I am seeing. And as I've said, I can 
not delete NSR peer information for the *server*, at least not from the 
server. I can (and have, many times) deleted NSR peer information for 
clients of the server, exactly as you've shown. But now I am getting 
"conflicting NSR peer information". Not "There is already" ...



> 
>    (Running automatically is left as an exercise to the reader).
> 
> On 08/09/2011 06:48 PM, Michael Leone wrote:
> > I've started seeing this message, and the host it is referring to is 
my
> > server (among other servers), I think I fix this the same way I fix 
the
> > error that says "There is already a machine with that name". That is,
> >
> > nsradmin -p nsrexec
> > Delete type: NSR peer information; name: server being complained about
> >
> > But I haven't been able to confirm that this is what I need to do. Can
> > anyone tell me if this is what I do, or is there some other method to 
fix
> > conflicting NSR peer info?
> >
> > Thanks
> >
> 

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER