I have no idea. Based on the lack of response that I received, I am
beginning to wonder if anyone on this list is using the Linux version. I
found a Red Hat 5.2 disk which based on the Tango Linux Getting Started
guide is supported and I'm going to give it a try.

I'm sorry to be a pain but if there is anyone that is successfully using
Tango Linux on any Red Hat version, could they please contact me.

Thanks,

Steve Smith

Oakbridge Information Solutions
Office: (519) 624-4388
GTA:    (416) 606-3885
Fax:    (519) 624-3353
Cell:   (416) 606-3885
Email:  [EMAIL PROTECTED]
Web:    http://www.oakbridge.ca


> -----Original Message-----
> From: Bill Conlon [mailto:[EMAIL PROTECTED]
> Sent: February 27, 2003 6:17 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Witango-Talk: Red Hat Linux
>
>
> You inspired me to try this out on my dev server (Suse Linux 6.4 = 2.2.14
> kernel).
>
> So I followed instructions:
>
> Installed successfully from an rpm, v 4.00.088 was installed and launched.
>
> downloaded, configured, compiled, made, installed apache_1.3.27 with the
> tango4 app server, including httpd.conf.
>
> Updated to the 4.05.047 FTF, and t4event.log shows it running with a 30
> day license, but every attempt to access a simple hello.taf or the
> config.taf fails:
>
> apache error_log (ten entries similar to below):
> [Thu Feb 27 14:13:30 2003] [notice] child pid 1662 exit signal
> Segmentation fault (11)
>
> Any thoughts on obvious things to do?
>
> >I'm in a 'get this Linux thing to work' mood again this week. I had
> >installed Red Hat Linux 7.3 and was able to get the Tango Server
> to work by
> >connecting from a Tango Windows client, the Tango client to work by
> >connecting to a Tango Windows server (cgi method only, not
> plug-in), and got
> >the two of them to talk to each other but again with only the cgi and not
> >the plug-in. And I couldn't get the Tango Linux server to talk to MySQL.
> >
> >One of my former co-workers has it working on his Linux box but under Red
> >Hat Linux 6.2 (and using PrimeBase I think, not MySQL). He suggested I'd
> >need to go back to 6.2 because the 7.3 libraries wouldn't work with Tango
> >2000. I managed to find the ISO files on a Red Hat mirror site and burned
> >the CD's but I can't get the CD to autoload. Does anyone have a
> suggestion
> >on how I might get around this problem?
> >
> >Does anyone have any experience using Tango 2000 under Red Hat
> 7.3 with the
> >plug-in? I'm also trying to get MySQL working under Linux but
> haven't been
> >able to get it to communicate either from Tango server running
> on the same
> >box or from a Tango server running on another box.
> >
> >If there are any Red Hat Linux gurus out there, I'd love to talk to them.
> >
> >Also what is the current status of the Witango Linux beta?
> >
> >I realize I've asked a bunch of different questions here, I'd be happy to
> >receive any responses that answer even some of my questions.
> >
> >Please let me know.
> >
> >Thanks,
> >
> >Steve Smith
> >
> >Oakbridge Information Solutions
> >Office: (519) 624-4388
> >GTA:    (416) 606-3885
> >Fax:    (519) 624-3353
> >Cell:   (416) 606-3885
> >Email:  [EMAIL PROTECTED]
> >Web:    http://www.oakbridge.ca
> >
> >
> >________________________________________________________________________
> >TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> >                with unsubscribe witango-talk in the message body
> >
>
>
> Bill Conlon
>
> To the Point
> 345 California Avenue Suite 2
> Palo Alto, CA 94306
>
> office: 650.327.2175
> fax:    650.329.8335
> mobile: 650.906.9929
> e-mail: mailto:[EMAIL PROTECTED]
> web:    http://www.tothept.com
>
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
>                 with unsubscribe witango-talk in the message body
>

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

Reply via email to