LAMP error....!

PHP programming forum. Ask questions or help people concerning PHP code. Don't understand a function? Need help implementing a class? Don't understand a class? Here is where to ask. Remember to do your homework!

Moderator: General Moderators

Post Reply
tuXXer
Forum Newbie
Posts: 4
Joined: Wed Jun 19, 2002 8:10 am

LAMP error....!

Post by tuXXer »

I have a LAMP (Linux - Apache -MySQL - Php) Problem. I've written a program that do following things:

- Clear directories
- Get information from database
- Write temporary XML file
- Transformation of XML file to XHTML file with Sablotron XSLT
- Delete XML file
- Show statistics

This works under Windows (Apache 2.0.36, Php 4.2.1, MySQL 4.0.1) without problems. Under Linux (Apache 1.3.23, Php 4.1.0, MySql 3.23.48) Php clear the directoies, write the XML file, transformate and then he does it in an infinite loop although the process stands in an constructor. The browser gives a message ("The page does not contain any data") back or writes "Host not found". Does anyone have a solution for this problem?
Zmodem
Forum Commoner
Posts: 84
Joined: Thu Apr 18, 2002 3:59 pm

Post by Zmodem »

LAMP? heh, never heard that one before. Cool

anyway, can we see some code please?
tuXXer
Forum Newbie
Posts: 4
Joined: Wed Jun 19, 2002 8:10 am

SEGEV!

Post by tuXXer »

Well it seems to be a segmentation fault error. When I remove the @ for dispressing the error messages then sometimes it run. Then it run when I give out the file I read, then not. The error log of Apache says "...Segmentation Fault...". Does anybody have equal problems?

P.S.: I think 1.200 lines in different classes don't make a sense for this forum...
User avatar
BDKR
DevNet Resident
Posts: 1207
Joined: Sat Jun 08, 2002 1:24 pm
Location: Florida
Contact:

LAMP stuff

Post by BDKR »

Hey Zmodem,

About LAMP, check out onlamp.com. I think the idea is a good one
even tough it's a little too highbrow seeming for me.

Now for tuXXer; Did you write this 1200 line monster? And besides, without a little bit
in the way of code, it's impossible to help.

I will make one suggestion. If the code is written in a modular fashion, test in a modular fashion. Get my drift? Also, if it works under one setup, but not another, it's hard to believe
it's a code issue. Break this thing down into the modules (or classes) that something this big had better be written in and test them individually on both configurations. A lot of work? Yes. But not everything is easily solved with a one liner and a smiley on a message board. :!:

Good luck and keep pluggin',
BDKR (TRC)

Later on,
BDKR (TRC)
Post Reply