<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: at job question in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/at-job-question/m-p/4505833#M38394</link>
    <description>&amp;gt;Don't want a cron entry since all of my cron is source controlled&lt;BR /&gt;&lt;BR /&gt;I would suggest you still use cron, it is meant for what you want to do.  Just one entry:&lt;BR /&gt;00 18 * * 0,1,3,4,5,6 command&lt;BR /&gt;&lt;BR /&gt;With at(1), you have to keep restarting it.  You could include your at(1) command within your script, with a check to ignore Tuesday.</description>
    <pubDate>Sat, 03 Oct 2009 17:01:35 GMT</pubDate>
    <dc:creator>Dennis Handly</dc:creator>
    <dc:date>2009-10-03T17:01:35Z</dc:date>
    <item>
      <title>at job question</title>
      <link>https://community.hpe.com/t5/operating-system-linux/at-job-question/m-p/4505830#M38391</link>
      <description>Hi Folks, &lt;BR /&gt;&lt;BR /&gt;I want to schedule multiple at jobs for different days - &lt;BR /&gt;&lt;BR /&gt;The job should run at 6pm everyday on wednesday, thursday, friday, sat, sun &amp;amp; mon.&lt;BR /&gt;How do I do that in Linux.&lt;BR /&gt;&lt;BR /&gt;Dont want a cron entry since all of my cron is source controlled and I dont want to touch that.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Allan</description>
      <pubDate>Wed, 30 Sep 2009 18:16:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/at-job-question/m-p/4505830#M38391</guid>
      <dc:creator>Allanm</dc:creator>
      <dc:date>2009-09-30T18:16:29Z</dc:date>
    </item>
    <item>
      <title>Re: at job question</title>
      <link>https://community.hpe.com/t5/operating-system-linux/at-job-question/m-p/4505831#M38392</link>
      <description>HI&lt;BR /&gt;&lt;BR /&gt;I'd put everything into a file and then just read the file every X hours.&lt;BR /&gt;&lt;BR /&gt;at [ [CC]YY]MMDDhhmm [ . ss ] -or-&lt;BR /&gt;at 200910010000.00 (* midnight 10/01 *)&lt;BR /&gt;at -f job-file&lt;BR /&gt;&lt;BR /&gt;Here's the format to follow for 'at' commands within the file&lt;BR /&gt;&lt;BR /&gt;-t spectime Define the absolute time to start the job.&lt;BR /&gt;spectime A date and time in the format:&lt;BR /&gt;[ [CC]YY]MMDDhhmm [ . ss ]&lt;BR /&gt;where the decimal digit pairs are as follows:&lt;BR /&gt;CC The first two digits of the year (19, 20).&lt;BR /&gt;YY The second two digits of the year (69-99, 00-68). See WARNINGS.&lt;BR /&gt;MM The month of the year (01-12).&lt;BR /&gt;DD The day of the month (01-31).&lt;BR /&gt;hh The hour of the day (00-23).&lt;BR /&gt;mm The minute of the hour (00-59).&lt;BR /&gt;ss The second of the minute (00-61).&lt;BR /&gt;If both CC and YY are omitted, the default is the current year.&lt;BR /&gt;If CC is omitted and YY is in the range 69-99, CC defaults to 19.&lt;BR /&gt;Otherwise, CC defaults to 20.&lt;BR /&gt;The range for ss provides for two leap seconds. If ss is 60 or 61, and&lt;BR /&gt;the resulting time, as affected by the TZ environment variable, does&lt;BR /&gt;not refer to a leap second, the time is set to the whole minute following&lt;BR /&gt;mm.&lt;BR /&gt;If ss is omitted, it defaults to 00.&lt;BR /&gt;time [date] Define the base time for starting the job.&lt;BR /&gt;time A time specified as one, two, or four digits. One- and two-digit&lt;BR /&gt;numbers represent hours; four digits represent hours and minutes.&lt;BR /&gt;Alternately, time can be specified as two numbers separated by a&lt;BR /&gt;colon (:), a single quote (â  ), the letter h (h), a period (.), or a comma&lt;BR /&gt;(,). Spaces may be present between the separator and digits&lt;BR /&gt;representing minutes. If defined in langinfo(5), special time unit&lt;BR /&gt;characters can be used.&lt;BR /&gt;am or pm can be appended to indicate morning or afternoon. Otherwise,&lt;BR /&gt;a 24-hour clock is understood. For example, 0815, 8:15,&lt;BR /&gt;8â  15, 8h15, 8.15, and 8,15 are read as 15 minutes after eight in&lt;BR /&gt;the morning. The suffixes zulu and utc can be used to specify Coordinated&lt;BR /&gt;Universal Time (UTC), equivalent to Greenwich Mean Time&lt;BR /&gt;(GMT).&lt;BR /&gt;The special names midnight, noon, and now are also recognized.&lt;BR /&gt;date A day of the week (fully spelled out or abbreviated) or a date consisting&lt;BR /&gt;of a day, a month, and optionally a year. The day and year fields&lt;BR /&gt;must be numeric, and the month can be either fully spelled out, abbreviated,&lt;BR /&gt;or numeric. The fields in the date string are separated by&lt;BR /&gt;punctuation marks such as slash (/), hyphen (-), period (.), and&lt;BR /&gt;comma (,). If defined in langinfo(5), special date unit characters can&lt;BR /&gt;Section 1-28 - 2 - HP-UX Release 11i: December 2000&lt;BR /&gt;a&lt;BR /&gt;at(1) at(1)&lt;BR /&gt;be present. A field having a value greater than 31 is treated as the&lt;BR /&gt;year field and the remaining two fields in the date string are treated&lt;BR /&gt;as month and day fields. Otherwise, if a given date is ambiguous (such&lt;BR /&gt;as 2/5 or 2/5/10), the D_T_FMT string (if defined in langinfo(5)) is&lt;BR /&gt;used to resolve the ambiguity.&lt;BR /&gt;Two special days, today and tomorrow, are also recognized. If no&lt;BR /&gt;date is given, today is assumed if the given time is greater than the&lt;BR /&gt;current time; tomorrow is assumed if it is less.&lt;BR /&gt;If the given month is less than the current month (and no year is&lt;BR /&gt;given), next year is assumed. Two-digit years in the range 69 to 99&lt;BR /&gt;are expanded to 1969 to 1999; in the range 00 to 68, to 2000 to 2068.</description>
      <pubDate>Wed, 30 Sep 2009 19:03:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/at-job-question/m-p/4505831#M38392</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2009-09-30T19:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: at job question</title>
      <link>https://community.hpe.com/t5/operating-system-linux/at-job-question/m-p/4505832#M38393</link>
      <description>HI Again&lt;BR /&gt;&lt;BR /&gt;Here's a better example&lt;BR /&gt;&lt;BR /&gt;at -f $HOME/jobfile -t201312271220.00</description>
      <pubDate>Wed, 30 Sep 2009 19:05:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/at-job-question/m-p/4505832#M38393</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2009-09-30T19:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: at job question</title>
      <link>https://community.hpe.com/t5/operating-system-linux/at-job-question/m-p/4505833#M38394</link>
      <description>&amp;gt;Don't want a cron entry since all of my cron is source controlled&lt;BR /&gt;&lt;BR /&gt;I would suggest you still use cron, it is meant for what you want to do.  Just one entry:&lt;BR /&gt;00 18 * * 0,1,3,4,5,6 command&lt;BR /&gt;&lt;BR /&gt;With at(1), you have to keep restarting it.  You could include your at(1) command within your script, with a check to ignore Tuesday.</description>
      <pubDate>Sat, 03 Oct 2009 17:01:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/at-job-question/m-p/4505833#M38394</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-10-03T17:01:35Z</dc:date>
    </item>
  </channel>
</rss>

