For the project that was talked about here -> Controlling USB on Raspberry Pi.
The software needs to open and close curtains at specified times each day. 8:30am and sunset. So it really only needs to be active a couple of times each day but those times change. One always does and the other potentially will in the future.
From a design viewpoint this seems to leave three options:
- Script runs a continuous loop
- CRON kicks it into life ever few (5?) minutes
- Script writes to CRON the next time it needs to fire up
It seems to me that 1 is not such a good plan because, if for any reason the script were to fail, the system fails and doesn't restart. 2 would mean that the granularity of times the curtains could actually change state is quite big as set by CRON. Although this is not a big issue for this project I am trying to build something using sound design principles. Which leaves 3 which prevents the next event being changed. Again not a problem here but perhaps not the best design.
Gut feeling is that 2 is the way to go but I'm failing to convince myself...
Which one of these, combination of these or some other option I have not considered would you choose?
-
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.
|
