At 03:58 PM 7/30/2012 -0400, Jared Camins-Esakov wrote: [snip]
However, using a normal sudo account for crontab -e, use vi, add:
KOHA_CONF=/etc/koha/koha-conf.xml KOHAPATH=/usr/share/koha PERL5LIB=$KOHAPATH/lib * * * * *  koha  $KOHAPATH/bin/migration_tools/<http://rebuild_zebra.pl>rebuild_zebra.pl -a -b -z 2>&1 > /dev/null
makes a fully functional cron for incrementing Zebra, albeit in /var/spool/cron/crontab/ with root:root ownership. All that remains to be done is to rename the koha file in /etc/cron.d to koha.old (or plain remove it.) [N.B. the job is quasi-instantaneous, so running every minute is imperceptible as overhead.]
The ownership of the file doesn't matter. What matters is that you shouldn't have this configured in two different crontabs, which you currently do. This may cause problems.
Very minor point: I wrote "All that remains to be done is to rename the koha file in /etc/cron.d to koha.old (or plain remove it.)" I should have said that I already did it: paul@server2:/var/log$ sudo cat syslog | grep CRON Jul 30 16:09:01 server2 CRON[3345]: (root) CMD (koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z 2>&1 > /dev/null) Jul 30 16:10:01 server2 CRON[3351]: (root) CMD (koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z 2>&1 > /dev/null) Jul 30 16:11:01 server2 CRON[3354]: (root) CMD (koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z 2>&1 > /dev/null) Also thanks for correcting the Wiki, but there was something strange going on (char set glitch?) Copy/paste from Firefox to Putty screen gives: perl .I /usr/share/koha/lib /usr/share/koha/bin/migration_tools/rebuild_zebra.pl .b .w Not the "." rather than "-" for I, b and w I did an edit, which worked in the "show preview" so I saved it. Best - Paul