Re: Solved problem -916 errors in remote events
Re: Solved problem -916 errors in remote events
- Subject: Re: Solved problem -916 errors in remote events
- From: email@hidden
- Date: Mon, 12 Nov 2001 20:42:52 -0500
Bill,
Well - I consider myself braver than most - and I even think I know more
than the average scripter at times, but I can't seem to follow you. I
did step 1 on your list, but it didn't do anything for my errors. And
when I try step 2, all I get is:
Expecting equal "=" at line 1
I tried playing with the text file thinking copy and paste may have done
some wacky stuff, but I can't seem to get it. Is there something you
maybe left out of the ni.txt - or some other step - that would make this
work right. I would love to get this working.
Thanks,
Tyler
On Monday, November 12, 2001, at 12:25 PM, applescript-users-
email@hidden wrote:
I finally solved the problem, still trying to decide if it's a bug and
waiting for bugreporter to come back up.
If the machine you're connecting to, "eppc://10.0.1.53" in my case, can
not be resolved in DNS on the host instantiating the connection
Applescript returns error -916 (system error port was closed).
From my previous testing I knew something odd was going on because I
had
one machine that could talk to others but nothing could talk to it. It
finally hit me, I had set up host entries on the working box for all the
machines on my network to stop the annoying lookupd failures in the
system.log
I've done several tests and it appears all that is needed is host
entries for the machines you're sending events to.
You should modify lookupd to use the FFAgent as well but it's not
required in order to make it work. Below is how to configure both:
1) adding host entries is pretty easy.
open /etc/hosts in your favorite editor. If you're not into vi, this
will work for you:
sudo open -e /etc/hosts
add entries as needed. host entries are of the form: ipaddress hostname
ex. 10.0.1.53 lilith
2) Setting up lookupd to use flat files before DNS (again this is not
necessary but makes lookupd use /etc/hosts as well)
I prefer maintaining an /etc/hosts file over netinfo. You can modify it
quick and easy. I suppose I could have written a script to insert the
netinfo records but I'm lazy ;)
put the following in a text file called ni.txt
{
"name" = ( "locations" );
CHILDREN = (
{
"LookupOrder" = ( "CacheAgent", "FFAgent", "DNSAgent",
"NIAgent" );
"name" = ( "lookupd" );
CHILDREN = (
{
"LookupOrder" = ( "CacheAgent", "FFAgent", "DNSAgent",
"NIAgent" );
"name" = ( "hosts" );
}
)
}
)
}
now load the file into netinfo
sudo niload -d -r /locations . < ni.txt
restart lookupd (or restart you're machine, but shame on you for
restarting OSX)
sudo kill -HUP `ps -aux | grep lookupd | grep -v grep | awk '{ print
$2 }'`
lookupd -configuration should show:
LookupOrder: CacheAgent FFAgent DNSAgent NIAgent
hope this helps,
-Bill