On Sat, 20.07.13 09:00, Robert Nichols (rnicholsNOSPAM@xxxxxxxxxxx) wrote: > On 07/15/2013 09:14 AM, Lennart Poettering wrote: > >This feature is about not doign local mail delivery by default, by not > >installing any MTA. Instead you find the log output of cronjobs at the > >same place as you find any other log output, the journal/syslog, for > >example accessible via: > > > >journalctl -u crond > > > >or > > > >systemctl status crond > > > >(the latter will only show you 10 log lines by default, the former all > >of them. You can pass "-n 100" to either to see the 100 latest ones) > > You are thinking only about error output from cron jobs. Regular > output from cron jobs can be quite voluminous. Is it reasonable to send > 15 to 20 Kilobytes to the journal (root's logwatch job currently sends > that much every day)? How about a couple of JPGs (graphs of resource > usage)? The journal supports 2^64 sized binary objects to be stored in it. It currently will get a bit slow if you actually send a lot of data sind it first needs to XZ compress the blobs before writing them to disk and that will stall operation for that time, but a few 100K (or even MB) in a single message should be no problem. (Note that the way cron's mail support works you cannot use it directly to send JPEGs...) Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
