<?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 Automating in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170094#M681933</link>
    <description>Guru's last question today I promise.&lt;BR /&gt;&lt;BR /&gt;I am running a command line virus scanner. So I set a cronjob to run it every sunday at 4:30 PM and send the output to a file in my homdir as below:&lt;BR /&gt;&lt;BR /&gt;#30 16 * * 0 /usr/local/bin/uvscan/uvscan &amp;gt;&amp;gt; /home/name/scanresults&lt;BR /&gt;&lt;BR /&gt;My question is how would I have these scan results automatically sent to my outlook e-mail address? Would I just put it is the crontab after the &amp;gt;&amp;gt; /home/name/scanresults? something like :&lt;BR /&gt;&lt;BR /&gt;mail -s 'Subject' somewhere@domain.com &amp;lt; /home/name/scanresults  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;or is there an easier/better way?</description>
    <pubDate>Thu, 16 Apr 2009 17:27:01 GMT</pubDate>
    <dc:creator>Adam W.</dc:creator>
    <dc:date>2009-04-16T17:27:01Z</dc:date>
    <item>
      <title>Automating</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170094#M681933</link>
      <description>Guru's last question today I promise.&lt;BR /&gt;&lt;BR /&gt;I am running a command line virus scanner. So I set a cronjob to run it every sunday at 4:30 PM and send the output to a file in my homdir as below:&lt;BR /&gt;&lt;BR /&gt;#30 16 * * 0 /usr/local/bin/uvscan/uvscan &amp;gt;&amp;gt; /home/name/scanresults&lt;BR /&gt;&lt;BR /&gt;My question is how would I have these scan results automatically sent to my outlook e-mail address? Would I just put it is the crontab after the &amp;gt;&amp;gt; /home/name/scanresults? something like :&lt;BR /&gt;&lt;BR /&gt;mail -s 'Subject' somewhere@domain.com &amp;lt; /home/name/scanresults  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;or is there an easier/better way?</description>
      <pubDate>Thu, 16 Apr 2009 17:27:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170094#M681933</guid>
      <dc:creator>Adam W.</dc:creator>
      <dc:date>2009-04-16T17:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: Automating</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170095#M681934</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;Any output (STDOUT or STDERR) that is not redirected (to a file) when executed in a 'cron'd task is sent to the user as mail.&lt;BR /&gt;&lt;BR /&gt;Hence, you could setup a '.forward' file in your ${HOME} directory that contains the line:&lt;BR /&gt;&lt;BR /&gt;somewhere@domain.com&lt;BR /&gt;&lt;BR /&gt;The '.forward' should be owned by the user and readable only by the same.&lt;BR /&gt;&lt;BR /&gt;Otherwise, the 'mail' syntax you showed would also work.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Thu, 16 Apr 2009 17:39:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170095#M681934</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-04-16T17:39:57Z</dc:date>
    </item>
    <item>
      <title>Re: Automating</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170096#M681935</link>
      <description>Hi (again) Adam:&lt;BR /&gt;&lt;BR /&gt;By the way, as a 'sendmail' requirement you must (of course) have the 'DJ' macro ("smart relay") defined in your '/etc/mail/sendmail.cf' something like:&lt;BR /&gt;&lt;BR /&gt;DSexchange.domain.com&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Thu, 16 Apr 2009 17:42:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170096#M681935</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-04-16T17:42:45Z</dc:date>
    </item>
    <item>
      <title>Re: Automating</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170097#M681936</link>
      <description>James,&lt;BR /&gt;    Unfortunately, we cannot have .forward file on our systems (Government regulation) we are allowed .alias files though. I could, in theory set it up the same yes?</description>
      <pubDate>Thu, 16 Apr 2009 17:49:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170097#M681936</guid>
      <dc:creator>Adam W.</dc:creator>
      <dc:date>2009-04-16T17:49:32Z</dc:date>
    </item>
    <item>
      <title>Re: Automating</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170098#M681937</link>
      <description>but I digress. James, just to confirm if I did :&lt;BR /&gt;&lt;BR /&gt;#30 16 * * 0 /usr/local/bin/uvscan/uvscan &amp;gt;&amp;gt; /home/name/scanresults mail -s 'scanresults' me@mine.com &lt;BR /&gt;&lt;BR /&gt;would it work?</description>
      <pubDate>Thu, 16 Apr 2009 17:54:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170098#M681937</guid>
      <dc:creator>Adam W.</dc:creator>
      <dc:date>2009-04-16T17:54:53Z</dc:date>
    </item>
    <item>
      <title>Re: Automating</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170099#M681938</link>
      <description>Hi (again) Adam:&lt;BR /&gt;&lt;BR /&gt;&amp;gt; we are allowed .alias files though. I could, in theory set it up the same yes?&lt;BR /&gt;&lt;BR /&gt;Yes, see the '/etc/mail/aliases' file.  You might just as well 'cron' something like:&lt;BR /&gt;&lt;BR /&gt;# 30 16 * * 0 /usr/local/bin/uvscan/uvscan|mailx -s "The Subject" somewhere@domain.com&lt;BR /&gt;&lt;BR /&gt;...eliminating the temporary file.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Thu, 16 Apr 2009 17:56:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170099#M681938</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-04-16T17:56:41Z</dc:date>
    </item>
    <item>
      <title>Re: Automating</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170100#M681939</link>
      <description>ah, ya know what I didn't even think about it. For some reason I was thinking I HAD to send it to a file first. But then again, that is why your a guru and I am not. James, thank you (yet again) with all of your help.</description>
      <pubDate>Thu, 16 Apr 2009 17:58:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170100#M681939</guid>
      <dc:creator>Adam W.</dc:creator>
      <dc:date>2009-04-16T17:58:25Z</dc:date>
    </item>
    <item>
      <title>Re: Automating</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170101#M681940</link>
      <description>James, once again always a pleasure. Thanks for the help.</description>
      <pubDate>Thu, 16 Apr 2009 18:02:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170101#M681940</guid>
      <dc:creator>Adam W.</dc:creator>
      <dc:date>2009-04-16T18:02:33Z</dc:date>
    </item>
    <item>
      <title>Re: Automating</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170102#M681941</link>
      <description>&amp;gt;JRF: /usr/local/bin/uvscan/uvscan | mailx -s "The Subject" ...&lt;BR /&gt;&lt;BR /&gt;If you want to also send stderr you would need to do:&lt;BR /&gt;/usr/local/bin/uvscan/uvscan 2&amp;gt;&amp;amp;1 | mailx -s "The Subject" ...</description>
      <pubDate>Fri, 17 Apr 2009 04:02:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/automating/m-p/5170102#M681941</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-04-17T04:02:29Z</dc:date>
    </item>
  </channel>
</rss>

