d88-jwa@nada.kth.se (Jon W{tte) (02/24/91)
Okay, a rerun. INIT complains about inetd respawning too rapidly. The solution, previously, was said to be "newconfig appletalk" or "newconfig nfs" - nope, no go. I've checked the syntax of servers and the validity of the programs there referenced, as compared to the distribution. Trying "talk" yields: [Couldn't bind to control socket : Can't assign requested address (69)] I think this is a symptom of inetd not running... But it could be symptomatic of something else, causing inetd to fail. Running the thing by itself terminates in about no time at all with status 0. This is on an 8 Mb IIfx running 2.0 installed from the CD (and I have some symbolic links out to the ROM to save space) Any help appreciated, since I'd like to use Berkley sockets... Jon (By the way, I haven't used my toll-free support yet, since I can't dial 800 from Sweden. What do I do instead ?) -- "The IM-IV file manager chapter documents zillions of calls, all of which seem to do almost the same thing and none of which seem to do what I want them to do." -- Juri Munkki in comp.sys.mac.programmer
alexis@panix.uucp (Alexis Rosen) (02/24/91)
I was plagued by this stuff for a long while. Talk's ridiculous error messages
didn't help much either.
What finally fixed things for me was a change I made to my /etc/hosts file.
If you have no ethernet connection, the first line (loopback) has to contain
your hostname, which must come before any other aliases on that line. If you
do have ethernet, you need to add a line which contains your hostname and its
address.
There are lots of other ways things can get screwed up, but since this stuff
is broken by default, it's the most likely thing to need fixing.
Also, I _know_ I don't have the whole story on this one. If anyone else learns
more details, please let me know...
---
Alexis Rosen
Owner/Sysadmin, PANIX Public Access Unix, NY
{cmcl2,apple}!panix!alexisalexis@panix.uucp (Alexis Rosen) (02/27/91)
[This is a repost. I'm pretty sure it didn't make it out the first time.]
I was plagued by this stuff for a long while. Talk's ridiculous error messages
didn't help much either.
What finally fixed things for me was a change I made to my /etc/hosts file.
If you have no ethernet connection, the first line (loopback) has to contain
your hostname, which must come before any other aliases on that line. If you
do have ethernet, you need to add a line which contains your hostname and its
address.
There are lots of other ways things can get screwed up, but since this stuff
is broken by default, it's the most likely thing to need fixing.
Also, I _know_ I don't have the whole story on this one. If anyone else learns
more details, please let me know...
---
Alexis Rosen
Owner/Sysadmin, PANIX Public Access Unix, NY
{cmcl2,apple}!panix!alexis