Chris H. wrote:
[snip]
While it
didn't fix my seeming php5 module number limitation. I was able, after
trial and error, to discover that the recode module was the module
causing Apache to dump core. Simply removing it from the list cured
it. :) Further investigation reveals that there are some is
I saw a thread last month about the servers that build INDEX files being
down since the security incident - is that still the case?
The files obtained via make fetchindex are still out of date, so I
assume they're still off, but a while back they were just missed after
some maintenance as well so
>> On 13 Dec 2012 16:57, "Jim Pingle" wrote:
>> I saw a thread last month about the servers that build INDEX
files being
>> down since the security incident - is that still the case?
>
> On 12/13/2012 6:35 PM, Simon L. B. Nielsen wrote:
> I had forgot
On 6/26/2013 2:40 AM, Baptiste Daroussin wrote:
> No the justification is that we use to have a perl-after-upgrade script to
> workaround the fact that we used major.minor.patchlevel my bypassing the
> package
> tool to modify directly the content of the package database and more some
> files
> o
On 07/02/13 07:10, Matthias Apitz wrote:
> El día Monday, July 01, 2013 a las 08:05:37PM -0700, Jeffrey Bouquet
> escribió:
>
>> bsdstats.org > ports stats would have that information probably
>
> http://bsdstats.org/ports.php?category=91
>
> says in column 'times in use':
>
> x11/kde3: 534
> x11/k
On 7/8/2013 11:40 AM, Sergio de Almeida Lenzi wrote:
> Yes it is broken,
>
> the logic that finds how much real memory is there in the FreeBSD
> is broken, reports ZERO..
>
> There is a Problem Report and a person that
> says will fix it, 2 weeks ago...
>
> I am using the last version 4.2.12 tha
On 4/9/2014 2:09 PM, John Marino wrote:
> On 4/9/2014 19:56, Christian Weisgerber wrote:
>> On 2014-04-08, Tijl Coosemans wrote:
>>> Then, once it is reasonable to assume that a port is unused it is first
>>> marked deprecated which gives users some time to step forward.
>>
>> There seems to be t
