comment on

I had to develop a comparably complicated perl based scheduler running on Windows used for running QA GUI scripts. Some points :

1. Use perl2exe in order to generate the executables - not need to deploy Perl to all workstations (if you have them more ; )

2. Do not put all the eggs into one basket - one executable starting the daily cycle and rebooting according to the times in the settings file

3. Produce different executables for the Daily Cycle, Hourly cycle .. etc.

4. Timing related code into a Timer.pm - array of hashes to store the dynamicly generated times according to the cycle length

5. Process handling and killing - in separate modules

6. Do not use fork , use CAREFULLY perl threads combined with

 
use Win32::Process ;
    Win32::Process::Create( $proc_o, "$proc_path", "" , 0,
    CREATE_NO_WINDOW ,$dir_where_to_run);
[download]

7. Use a simple xml file in order to keep track of the whole system

8. Many other small tricks - send me e-mail First.Last@gmail.com if need more information

9. The whole think has worked already 4 months 24/7 without any serious failures ...

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks