Very Computer

what's more interesting, though, is that i grabbed the termtelnet binary
from sunsite, and it works with no problems.  termftp, termwhois, and
termfinger all compiled from the source (again on sunsite) with no problems
at all.  *shrug*  i _do_ remember getting the "Failed to connect to Term
socket" errors for a little while though.. some change cleared it up.  let
me know if you want to see any of the patches i made, as those should
show you exactly what needs to be done.

jason

TERMDIR and TERMSHARE are both set to /usr/local/lib/term.  Permissions
on /usr/local/lib/term are global everything (as I'm the only user at
this point [until I had things working]).

When TERMMODE=1, all Term applications (compiled post-2.0 and pre-2.0)
quit with a "Connect: invalid argument."  When TERMMODE=0,  the pre-2.0
apps work ... the post-2.0 cannot connect to
/usr/local/lib/term/.term/socket.  A further error message is
given: 'Connect: bad file number.'  Permissions on socket are, again, global
everything.

I'm pretty sure that the fault is not on the server end, either.  I've
tested it on two separate servers (AIXESA and ULTRIX).  In both cases
the termrc matches between client and server, and I verify that both ends
are using the correct termrc via the startup message.  Identical results
with both servers.

Unless I've missed something, there is no logical reason for a) post-2.0
ported apps to not function, and b) shared mode not to operate at all.

Comments?

-- Chris

       "... but I want to use all eight comm ports SIMULTANEOUSLY!"
   PGP 2.6 public key available by finger for the clinically paranoid.

: I would welcome any e-mail along the lines of "you idiot!  All you have
: to do is XYZ ..."  I have to justify the time I wasted to my fiancee
: _somehow_.

Hmmm... you might be having the same problem I am. Whenever I
start term, I go into ~/.term and there are 2 socket files.
One called socket and the other is "socket " (with a space after
it. To solve it I just rm the socket file and then mv "socket "
to socket. Works fine after that.

I've gotten ncftp, ftp, fsp, Mosaic, Chimera, etc... etc.. working
with 2.0.3 and 2.0.4

Peter Sigler

: TERMDIR and TERMSHARE are both set to /usr/local/lib/term.  Permissions
: on /usr/local/lib/term are global everything (as I'm the only user at
: this point [until I had things working]).

: When TERMMODE=1, all Term applications (compiled post-2.0 and pre-2.0)
: quit with a "Connect: invalid argument."  When TERMMODE=0,  the pre-2.0
: apps work ... the post-2.0 cannot connect to
: /usr/local/lib/term/.term/socket.  A further error message is
: given: 'Connect: bad file number.'  Permissions on socket are, again, global
: everything.

: I'm pretty sure that the fault is not on the server end, either.  I've
: tested it on two separate servers (AIXESA and ULTRIX).  In both cases
: the termrc matches between client and server, and I verify that both ends
: are using the correct termrc via the startup message.  Identical results
: with both servers.

: Unless I've missed something, there is no logical reason for a) post-2.0
: ported apps to not function, and b) shared mode not to operate at all.

: Comments?

Do you have termrc in /usr/local/lib/term?

--
Yasuo Ohgaki

: Subject basically says it all.
Do you read the announce news group???
The authours went to great lengths to point out that 1.19 was
super-stable but 2.0.x were VERY EARLY beta.

luyer

: Do you read the announce news group???
: The authours went to great lengths to point out that 1.19 was
: super-stable but 2.0.x were VERY EARLY beta.

I suppose I could cop out by replying that I didn't see such a posting
(true, believe it or not).

My post should be interpreted as the result of two weeks (now nearing
three) of damn near non-stop compile,recompile, configure, reconfigure,
etc. on Term.  Dan Gasparovski responded and we're now trying to nail
down the problem.

-- Chris

       "... but I want to use all eight comm ports SIMULTANEOUSLY!"
   PGP 2.6 public key available by finger for the clinically paranoid.

Quote:> I have spent two weeks trying to get various incarnations of 2.x working
> properly.  I was overjoyed to see that TREDIR started working properly
> with release 2.0, and was ecstatic to find that I wouldn't have to rework
> the net routines in a given app to make it work right.

--

Louisiana Tech University, BSEE/Sr * These opinions are probably mine