On Fri, Nov 11, 2005, Steffen Weinreich wrote:
I´m fighting with mysql on debian 3.1 for some days now. What I have
found is the following:
- A build on a fresh installation of Debian 3.1 and OPenPKG 2.5
produces a mysqld with bails out with a Sig11 directly after
start.
- The
On Fri, Nov 11, 2005, Ralf S. Engelschall wrote:
So, my suggestion is: try to apply the following hunk from db.patch
to the mysql local copy of Berkeley-DB (in subdir bdb/):
Index: os/os_open.c
--- os/os_open.c.orig 2004-09-28 18:46:57 +0200
+++ os/os_open.c2004-11-11 20:04:31 +0100
Ralf S. Engelschall wrote:
On Fri, Nov 11, 2005, Ralf S. Engelschall wrote:
So, my suggestion is: try to apply the following hunk from db.patch
to the mysql local copy of Berkeley-DB (in subdir bdb/):
Index: os/os_open.c
--- os/os_open.c.orig 2004-09-28 18:46:57 +0200
+++ os/os_open.c
OpenPKG Version Tracking Report
===
Reporting Time:2005-11-11 19:32
Tracking Duration: 1:07:17 (H:M:S)
Tracking Input:1717 sources (909 packages)
Tracking Result: 1633 up-to-date, 32 out-dated, 52 error
The following 32 sources were determined to be
Was this patch from June ever considered? It's still a problem.
On Sun, Jun 19, 2005, Bill Campbell wrote:
The attached patch for postgresql addresses a long-standing
problem with postgresql in which it doesn't restart after an
abnormal termination (e.g. system reboot after power loss).
The
