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 it is here: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4873 and it looks like it should be in 3.6
Thanks - I've had a quick look, comparing our production 3.6.1 on Ubuntu 11.04 and sandbox 3.6.6 (absolutely clean install, server and Koha) on Ubuntu 12.04 LTS. This is a show stopper at the moment, as zebra (idzebra-2.0) obviously is non-functional. 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) b) dir/file structure differs after boot 3.6.1: drwxrwxrwt 4 root root 80 2012-07-24 07:50 lock drwxr-xr-x 18 root root 620 2012-07-24 07:50 run lock has two dirs apache2 and koha run has a koha 3.6.6: lrwxrwxrwt 1 root root 9 May 29 17:37 lock -> /run/lock lrwxrwxrwt 1 root root 4 Jul 23 20:31 run -> /run lock has two dirs apache2 and lvm, but no koha run has no koha Note that the 2 dirs run and lock are time/dated from this morning (I rebooted), but the two links in 12.04 / 3.6.6 are dated not from today's reboot, but presumably from the Ubuntu ISO. I'm thinking of trying something along the lines of: sudo mkdir /run sudo mkdir /run/lock sudo mv /var/run/* /run sudo mv /var/lock/* /run/lock sudo rm -rf /var/run sudo rm -rf /var/lock sudo ln -s /run /var/run sudo ln -s /run/lock /var/lock and then copying the relevant run and lock 'koha' files from the production Koha system, but might screw up badly ;={ Where to next, please? Thanks and br, Paul