[ic] How to use the other perl?

[Doug Alcorn]

"Voodoo" <voodoo@idola.net.id> writes:

> I thought it was a binary, just like the catalog that reside in
> cgi-bin dir.

While we're on the subject.  Let me waste some bandwidth explaining
that binary in cgi-bin.  It doesn't really do anything.  It's whole
purpose is just as a conduit between apache and the interchange
daemon.  The cgi-bin isn't responcible for anything that is catalog
specific.  What it does do is compile into the binary the location of
either the socket file (/usr/local/interchange/etc/socket for
instance) or the tcp port (I don't remember offhand which port it
is).

The reason I spell all this out is because sometime your cgi-bin file
may get lost or corrupted.  Armed with this information, you can just
copy one of the other catalog binaries over.  Also, in your
interchange/src dir you will find your compiled binaries.  In my
directory, I see two files tlink.localhost.7786 and
vlink._usr_local_interchange_etc_socket.   This is to show that the
tlink program is compiled to use tcp on port 7786 to the local host
and vlink is compiled to use /usr/local/interchange/etc/socket.

I've blathered enough about this.  I hope I have't annoyed anyone.
-- 
 (__) Doug Alcorn (mailto:doug@lathi.net http://www.lathi.net)
 oo / PGP 02B3 1E26 BCF2 9AAF 93F1  61D7 450C B264 3E63 D543
 |_/  If you're a capitalist and you have the best goods and they're
      free, you don't have to proselytize, you just have to wait.