Dear VAST community,
 I just was a little surprised by the behaviour or SstCron. It was just a matter of a couple of minutes to find the solution, but I wanted to share it here. I wanted to set up a daemon that does some logging of system state (AbxProcessPeakDumper  thanks John for this Goodie!) every minute. So I set up a Cron job like this: SstCron default add: ( You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at https://groups.google.com/group/vasmalltalk. For more options, visit https://groups.google.com/d/optout. 
Administrator

On Thursday, March 30, 2017 at 12:55:51 AM UTC7, Joachim Tuchel wrote:

Hi Joachim, I know nothing about the SST implementation of cron, but the Unix specification is a comma separated list of numbers for each aspect or an asterisk. e.g. every 10 minutes would use 0,10,20,30,40,50 for the minutes specification. I have my doubts that "minutes: 1" really did what you thought it did, but that it coincidentally worked as you wished. I don't know what it would have done had you coded "minutes: 10".
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at https://groups.google.com/group/vasmalltalk. For more options, visit https://groups.google.com/d/optout. 
Well,
 it turns out it didn't do what I wanted, because it ran the Block every single second of every minute. What SstCron does it it converts the Integer into an interval from: 0 to: 59 by: @myInteger. So looking only at the minutes, SstCron does exactly what I tell it: run the Block every @myInteger minutes of the hour(s). So I am not complaining about the part that I told SstCron about. It's more the part I said nothing about ;) If I understand correctly, Unix Cron won't run a job every second if you give an asterisk for the seconds. On the other hand, I also didn't give SstCron an asterisk, I just didn't specify. On the third hand, I didn't complain about SstCron running the job every minute of every hour, although I also hadn't specified anything abouot hours... Maybe this is just something you (or better: I ) need to be aware of and all is good... Joachim Am Donnerstag, 30. März 2017 21:52:02 UTC+2 schrieb Richard Sargent:
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at https://groups.google.com/group/vasmalltalk. For more options, visit https://groups.google.com/d/optout. 
Free forum by Nabble  Edit this page 