Re: Working! - Re: user crontab

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 5/8/20 2:08 AM, Cameron Simpson wrote:
On 08May2020 01:44, Jon LaBadie <jonfu@xxxxxxxxxx> wrote:
On Fri, May 08, 2020 at 09:57:33AM +1000, Cameron Simpson wrote:
On 07May2020 15:01, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote:
> /ustr/sbin/mycron:
> #!/bin/sh
>
> currentDate="$(date +'%a %b %d %T %Y')"
> echo "From cron@localhost  "$currentDate >> /var/spool/mail/$USER

Put $currentDate inside the quotes. With echo it is less of an issue, but for many other commands you should exert more control over strings.  So as a
matter of practice:

   echo "From cron@localhost $currentDate"

If nothing else it prevents filename expansion happening to the value of $currentDate. (Not that that will happen with the date format chosen, but
again, as a general practice in scripting.)

In my mail files each message is followed by a blank line
before the next "From_" line.  Is that a requirement of
mbox format?  If so, it may be necessary to add it to
the crontab output.

Kinda. Depends on the thing parsing the mbox file. To avoid misparsing message body lines which themselves commance with "From " some things only consider a From_ line after a blank line. Others rely on ">" stuffing. It is all a mess.

You _do_ need to ensure the message at least ends with a newline, of the From_ won't be at the start of a line. So the previously posted script ensures that with the "echo" in "( cat; echo )". If you want to ensure a blank line you also need an additional "echo".

Working on it.  Plus I have to sed in a Date: line.

Or Robert could install an MDA and make it the MDA's problem :-)

What fun would that be?

Plus I have always thought of this as a deficiency in cron on a workstation.  Cron should work (report in this case) properly without needing something else (MTA) installed.  Maybe the developers will pick this up and do it right...



Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux