Re: [OPEN-ILS-DEV] sample opensrf crontab (patch/review)

[Bill Erickson]

On Sat, Dec 12, 2009 at 9:51 AM, Mike Rylander mrylan...@gmail.com wrote:

 I removed the explicit interpreter invocations from the action/trigger
 lines to normalize the style a bit.  Is there a reason for the cd 
 script style, such as a need to know the runtime directory?



Thanks, Mike.  The 'cd  script' layout is there to accommodate the scripts
that source oils_header.pl in the /openils/bin directory.  They haven't been
taught the BINDIR search/replace magic yet.  In most cases, though, it would
be trivial to drop the oils_header.pl requirement altogether and just pull
the needed functions into the individual scripts, since the
oils_header.plfunctions are all pretty small.  I'll take a look at
that...

-b


-- 
Bill Erickson
| VP, Software Development  Integration
| Equinox Software, Inc. / The Evergreen Experts
| phone: 877-OPEN-ILS (673-6457)
| email: erick...@esilibrary.com
| web: http://esilibrary.com

Please come by and visit the Equinox team
and learn more about Evergreen
ALA MidWinter
January 15-18, 2010
booth # 2064

Re: [OPEN-ILS-DEV] sample opensrf crontab (patch/review)

[Joe Atzberger]

 I removed the explicit interpreter invocations from the action/trigger
 lines to normalize the style a bit.


I think the direct invocation of the scripts is the correct style and will
work for those listed.  However now may be a good time to note that a bunch
of EG scripts that should be executable don't have that permission set
correctly.  I hit some 30+ of them in my working branch, and even committed
a little script to check for mis-permissioned scripts:

http://github.com/senator/OpenILS-Evergreen/commits/asterisk_dec2009

--joe