Hi guys, i'm trying to start apache using: apachectl start. But apache
simply won't start, configurations files seems ok. If I try httpd -X i
receive a Segmentation fault(core dumped).
Anyone know what this could be? Nor help debugging the core output?
Apache installed using ports/www/apache22
Performing sanity check on apache22 configuration:
Syntax OK
Starting apache22.
Then, apache will run for a moment, as I can see using ps -ax | grep httpd.
But, in a question of a second or two it isn't running.
What else can I do?
Thanks.
___
Sorry Nicole, but here in Brazil our government does not use pirated
software, and yes, they're changing to Open Source.
Well, sadly home users still use pirated software(windows). But I
guess this may be coming to an end, or not expanding, since the new
cheap computer for the poor people comes
I guess that what he actually means is that the file is too big. And
if there is some way to reduce it, so that it's easier(faster, less
bandwidth usage) to download.
I don't know what is the best way.
Pedro.
On 3/31/06, Bill Moran [EMAIL PROTECTED] wrote:
Darryl Hoar [EMAIL PROTECTED] wrote:
I don't know about compatibility with FreeBSD, but the Nintendo DS
Wi-Fi Adapter only works with the DS, and costs 50USD. For the same
50USD you can buy a simple Wi-Fi router. If the DS Wi-Fi adapter won't
work with FreeBSD, i guess you should go with the Wi-Fi router.(I
don't know if USB Wi-Fi
Hi, I´m developing a web app in C++. But it loads a huge amount of
from a Database to memory, and I can´t afford doing this everytime
someone asks for the page. Is there a way to make the program to keep
running, and reading requests made via CGI?
If it helps, i´m running FreeBSD 6.0 with Apache
I tried to compile the FreeBSD 6.0 kernle, but /usr ran out of space.
What can I do?
Now I can't even start X, so, what files should I remove(already
removed /usr/obj)?
Thakns in advance,
Pedro.
___
freebsd-questions@freebsd.org mailing list
Hi Bob,
I've seen this happening to a Dell server, that used a SCSI raid. One
disk was with a faillure, and this would lock up the machine. This
faillure however was not logged, because tthe SCSI raid controller
wouldn't send the apropriate signal to FreeBSD, since they were not
compatible. It
