There are many job-monitor systems out there for Unix and Linux, and one of the things they can regulate is “expected disk-space usage.” But they really can’t observe how much disk space any particular job is using, nor can they necessarily regulate it (even with quota). You need to know the jobs.
Many shops try to do job scheduling with crontabs, and they get into trouble because you really can’t predict the completion-time of one unit of work. You wind up either wasting time or doubling-up on resources.
So-called “workflow monitoring” systems can be surprisingly effective. The various components of what we call “jobs” can in fact all run as child-processes of a parent that is simply forking children and waiting for them to complete. Heck, if the workflow is predictable and unchanging, that can be how you run jobs with a great deal of control, e.g. driven by a Perl script. All the work is done under the auspices of one parent pid.
-
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.
|