I have doubts/concerns about the reliability of Brutus' cron, and/or the length of runs on Brutus, or both. I've added a runlog to gumpy.py that simply stores (1) local date/time (2) PID (3) message. Hopefully this will grant us some insights.
27 May 04 08:13:19 : 3044 : Gump Start-up. Arguments ['gumpy.py'] 27 May 04 08:13:38 : 3044 : Complete [1 cvs:0,run:1] The three messages are: 1) Start-up (w/ any arguments) 2) Completion w/ overall result (and individual ones for CVS and the Gump run) 3) Lock detected (hopefully Gump was already running) This file will be written to the Gump root directory. Note: Since gumpy.py is running when it calls CVS to update Gump itself, this is the one file that doesn't get automatically updated from CVS. I'll manually update it on Brutus (and others if/when I get time). regards, Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
