[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Apache not working
On Sat, Mar 14, 2009 at 11:13:49PM +0000, Patrick Welche wrote:
> On Sat, Mar 14, 2009 at 08:57:18AM +0200, Mihai Chelaru wrote:
> > Steven M. Bellovin wrote:
> >> OK -- I recompiled apr, apr-tool, and apache22, and it works again.
> >> The question now is why? What changed to break binary compatibility
> >> within -current, and what will that imply for 6.0?
> > IIRC, it was a semctl50 call that failed (happened the same for mono
> > package).
> Any idea on how to prevent the failure without a recompile? (I still haven't
> managed to extract my postgresql data. I didn't expect to need to pg_dumpall
> before upgrading the OS :-/ )
If you are desperate, you simply need to compile/run postgres against a version
of the OS prior to the time_t change, even easier if you still have the
Just keep some sets.tgz handy for moving back and then forward.
Definitely a pain in the arse though. I have that many xen domu that I never
seem to run out of a viable OS for whatever the task is at hand.
If you have xen, set up an outdated domu temporarily. Just make sure it's
time_t and dev_t have been bumped to 64 bit quantities.
Main Index |
Thread Index |