AW: [ic] newbie install on SuSE 9.0 problems

[Interchange]

THANK YOU Stephan!

Interchange-4.8.7 now running on SuSE 9.0 Professional.
Here's my setup:
*SuSE 9.0 Pro
*Apache2 (default SuSE install)
*Perl 5.8.1 installed from ActivePerl  tarball into ~interch/usr/local... 
   (The default is NOT to use treading.  The only thing I had to change 
   during configuration was the path. I simply changed it from default
   install of /usr/local/bin to ~/usr/local/bin.  And of course I added
   that as the first entry in my PATH.)
*Interchange installed to run under user interch

Regards,
Joe

Stephan Becker wrote:

>Joshep E Glenn wrote:
>  
>
>>I'm trying to install interchange-4.8.7 on SuSE 9.0 Professional. 
>>...
>># When the above test fails, it may be due to your ISP or some other #
>>    
>>
>mechanism blocking port 8786.
>  
>
>>...
>>Early in the attemped debug I deactivated the firewall, etc and went to
>>    
>>
>
>  
>
>>/etc/permissions.easy
>>...
>>I've seen a couple of threads about re-installing perl, so I guess I'll
>>    
>>
>
>  
>
>>do that for lack of
>>any better ideas.
>>
>>    
>>
>
>I´ve running Interchange ontop of SuSE 8.3 and with 9 there might be the
>same issues like I had with 8.3.
>The main issue here was to rebuild perl entirely ´cause the distribution
>contained a thredded version 5.something as far as I remember.
>Just deinstalling and installing the older one (4.6.1) looked like no
>good idea because most components of SuSE are depending on the default
>perl.
>If the problem is your perl, just download ActiveState Perl 4.6.1
>nonthredding and install it within your main interchange account. Tell
>/.configure of interchange where it resides and your done (well not that
>easy to succeed here but you got the picture, aren´t you ?)
>
>The default Port of interchange is 7786 ('MV'). This port should usually
>be free. Maybe the firewall configuration causes some problems as there
>were with early version of this SuSE feature. Since 8 I have never had
>any problems anymore in this area because as default it is simply
>switched off.
>And yes, if you use UNIX sockets, there should be no port issue at all
>with interchange.
>BUT ! Check the permissions of the socket file.
>
>The clue at last was cgi-bin file permissions.
>The link file generated by the interchange makecat script comes with
>suid bit set.
>Well, I´m no unix guru at all and those 's' bits are a lill´ bit of
>magic to be.
>But after setting the permissions to 755 there were no problems any
>longer.
>
>For my own sake I always check CGI configuration before I install
>anything depending on it.
>Sometimes servers are running weired configurations here.
>Deploy a sample cgi script (printenv) and check if you can call it as
>expeceted.
>After you get it running properly you´ll have all the answers in mind
>you need while working yourself through makecat´s questionair.
> 
>Have fun and good luck
>Stephan Becker
>
>Blue-iMotion Business Online
>Geschäftsstelle Wiesbaden
>Straße der Republik 28
>D-65203 Wiesbaden
>
>Privat (0611)   205 1027
>Mobil  (0163)   205 1028
>Fax/AB (012126) 78 23 25 37 oder (012126) STBECKER
>eMail  stephan.becker at blue-imotion.de
>www    http://www.Blue-iMotion.de
>
>[Diese E-Mail wurde vor Versand automatisch auf Viren überprüft]
>
>
>
>_______________________________________________
>interchange-users mailing list
>interchange-users at icdevgroup.org
>http://www.icdevgroup.org/mailman/listinfo/interchange-users
>
>  
>