Op 24-07-12 19:41, Paul schreef:
> There is no 'koha-common' in /etc/init.d (nor anywhere else) on either
> the production machine or the sandbox. [All the 'koha-common*' files are
> still in the original Koha packages.]
Oh, I think I misunderstood. I had the impression that you were running
from
At 05:35 PM 7/24/2012 +0200, Robin Sheat wrote:
Op 24-07-12 17:26, Paul schreef:
> a) both koha-common.init files have the bug4873 mod. They are both
> still in the "package" used during install, so how are they re-used on
> boot? (a 'find / -name' does not find them anywhere else)
It becomes /
Op 24-07-12 17:26, Paul schreef:
> a) both koha-common.init files have the bug4873 mod. They are both
> still in the "package" used during install, so how are they re-used on
> boot? (a 'find / -name' does not find them anywhere else)
It becomes /etc/init.d/koha-common when it's installed.
> b)
At 10:14 AM 7/24/2012 +0200, Robin Sheat wrote:
[snip]
The problem is that Ubuntu effectively clears the /var/lock directory on
boot, which Debian doesn't do. The patch (which is in now, maybe it
never made it into 3.6, I'm not sure) just creates
/var/lock/(instancename)/... on boot.
The bug for
Op 23-07-12 21:29, Paul schreef:
> I find in the records, that Chris C. had addressed this in June 2011
> "Your answer is here, you are missing those directories, you will need
> to create them and make sure they are writable by the user you run zebra
> as" and that Robin had followed up "There is
Yesterday, I took the plunge and installed 3.6.6 on a brand new install of
Ubuntu 12.04 server. Everything went swimmingly well ('restored' an old
Koha db, data conversion succeeded) until:
koha@sandbox:/usr/share/koha/bin/migration_tools$
KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/
