I'm in the process of comparing the Wiki page <http://wiki.koha-community.org/wiki/Koha_on_Ubuntu> with my own notes and am wondering if I am missing a "bigger picture" although I'm pretty sure my findings (3.8.4 on 12.04.1) are reliable. The Wiki suggests editing /etc/cron.d/koha to include KOHA_CONF=/etc/koha/koha-conf.xml, KOHAPATH=/usr/share/koha and PERL5LIB=$KOHAPATH/lib --- then "Alternatively you could ..." edit /etc/bash.bashrc.local to export KOHA_CONF and PERL5LIB I have found on 3.6 and 3.8 you must (rather than "alternatively could") add the two export lines to /home/koha/.bashrc [1] -- if not the variables are lost on reboot and the cron will fail (C4 not found.) The /etc/cron.d/koha does not need the env vars: paul@server: cat /etc/cron.d/koha */1 * * * * koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z &> /dev/null My notes: CONCLUSION: 3.8.4: cataloguing and zebra incremental cron fully functional. To renew PERL5LIB=/usr/share/koha/lib and KOHA_CONF=/etc/koha/koha-conf.xml after reboot, the 'export' must be in /home/koha/.bashrc; also /etc/cron.d/koha does not require any $ENV statements Am I missing something? tnx - paul [1] I tried all combinations of env vars in /home/koha/.bashrc and /etc/bash.bashrc.local, plus env vars or not in cron. I was a little surprised that the /etc/bash.bashrc.local did *not* restore the env vars to koha after reboot. Could someone running Debian Squeeze let me know if this is a Ubuntu or more general *deb problem? Or if there is a way of forcing 'local' to recognize user=koha?