[Koha-devel] zebraidx errCode=109

[Robin Sheat]

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) 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

I'm not sure what these are comparing. The Ubuntu boot process will
create /var/run and /var/lock, it's out of Koha's hands. The init script
should run koha-create-dirs however, which should create subdirs in that.

> 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

That sounds like a really bad idea. Let your OS do what it does and work
within that. Koha should be setting itself up to work within those
links. If not, it's a bug and should be fixed.

> and then copying the relevant run and lock 'koha' files from the
> production Koha system, but might screw up badly ;={

Noo. Lock and run files are temporary, transitive things. Often they
contain a PID which _will_not_ travel between systems meaningfully.

> Where to next, please?

Look in the init script, see if koha-create-dirs does what you need, if
not, amend it to do so and submit a patch.

-- 
Robin Sheat
Catalyst IT Ltd.
✆ +64 4 803 2204
GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D