Re: F20 - Unintended consequences of no default MTA - How best to fix

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

 



On 01/02/2014 10:08 PM, Chris Murphy wrote:
How big files can you send to the journal? The content we are talking about can be everything from oneliners to really long tracebacks.

By default it is compressed, and set to use 10% of free space. It's configurable, man journald.conf.

I meant how big files, i.e. content, can you send to the journal, not the size of journal itself. The content now sent via mail, that you want to be sent to the journal, can be quite voluminous. So what is the size limit of the content sent to the journal?

If it ends up in the journal, how will the user be informed that the content is in the journal and should (perhaps) be acted upon?

On Fedora 19 and older, when sendmail was the default, I was not ever informed of such things. Therefore the default installation of an MTA is orthogonal to actually successfully informing the user of anything.

Well, to be picky, you was informed, but you did not know were to look for the information you was informed about. This is (was) a lack in the documentation of Fedora. If this had been documented, you could have set up /etc/aliases and gotten informed.

But if this information now instead ends up in the journal, how to inform the user to look there?

If you want to do this correctly, you need a notification API. And I think Gnome at least has something like this now. For things like hard drives that die in a raid5, I see a banner alerting me of this fact, by default, in Gnome Shell. I don't know how that works but I don't think it's smartd that uses this API and informs Gnome. I think Gnome has it's own monitoring of such things. So either the program you want monitored needs to support such an API so it can issue a message for user notification in certain instances. Or maybe you need a configurable journal monitoring service that triggers notifications when certain priority messages appear in the journal.

Yes, that works for the desktop user.

But how do we do this in the use case of a home server? The user may not log into a graphical account that often. So how do we inform the user then?

Lars
--
Lars E. Pettersson <lars@xxxxxxxx>
http://www.sm6rpz.se/
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org




[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