Hi guys,<br><br>thanks for your input!<br><br>I think I will take the hard way, although I don't understand much of what was written. That particular "In C" piece is of a variable length, so a cron kill is not a good idea.
<br><br>Admittedly I thought there was an easy option "switch". But I will see if I can live up to that challenge! ;)<br><br>btw, I am from Germany, somewhere north of Frankfurt.<br><br><br><div><span class="gmail_quote">
2007/1/15, Kassen <<a href="mailto:signal.automatique@gmail.com">signal.automatique@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><div><span class="q"><span class="gmail_quote">On 1/15/07, <b class="gmail_sendername">Vassili Slessarenko</b> <<a href="mailto:urbanmuzak@urbanplexus.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
urbanmuzak@urbanplexus.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Wouldn't it actually be simpler to just run another cron job in how much<br></blockquote></span><div><br>More sensible -to me- would be scheduling ChucK itself to run when it's time to wake up. You could even make a snooze function that would silence it for five minutes after hitting the keyboard. This will also take care
</div></div></blockquote></div><br>