http://bugzilla.suse.com/show_bug.cgi?id=1117938 http://bugzilla.suse.com/show_bug.cgi?id=1117938#c1 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |fbui@suse.com --- Comment #1 from Franck Bui --- Hello, (In reply to Kristyna Streitova from comment #0)

Does it make any sense to you to pack this solution within the systemd package?

It seems that what is needed is already part of the functionalities provided by log monitoring systems, isn't it ? OTOH the solution brought by Arch is very limited and address a very specific use case, which I don't think we should officially support.

Or should we encourage users to create these scripts on their own? Or do you see any better solution?

Admittedly asking users to install a full log monitoring software (like graylog) for simply being notified when a unit fails is a bit cumbersome. Perhaps something like https://github.com/gkarakou/systemd-denotify would be more appropriated ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1117938 http://bugzilla.suse.com/show_bug.cgi?id=1117938#c3 --- Comment #3 from Franck Bui --- (In reply to Eric Schirra from comment #2)

Franck i think this package can not use for send a information mail when timer rise up errors.

Why not ? Maybe there's a confusion here: systemd timers are units that are supposed to activate *services* on a given time. So you're probably more interested in monitoring the service activated by the timer rather than the timer itself. And even if the timer unit itself fails that should be logged too. And to monitor services (and everything thrown in the journal), solutions (more or less complex) already exist. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1117938 http://bugzilla.suse.com/show_bug.cgi?id=1117938#c5 --- Comment #5 from Franck Bui --- (In reply to Eric Schirra from comment #4)

So, when systemd-denotify checks every 30min. It comes every 30min an error mesage. Not what i want or cron do. Please read the doc and conf of systemd-denotify.

Well the summary of the git repo [1] claims: A linux desktop app that notifies for user logins, failed systemd services, journal(log) patterns and optionally the status of selected services Please notice "failed systemd services, journal(log) patterns" part... And in the description of the project, "General" section says: These classes provide desktop and email notifications upon a user login, when systemd files are modified and when various patterns match in journal logs. So yes I did read the description of the project and it's pretty clear what the tool is supposed to achieved (and no I haven't looked at the code). [1] https://github.com/gkarakou/systemd-denotify -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1117938 http://bugzilla.suse.com/show_bug.cgi?id=1117938#c7 Kristyna Streitova changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kstreitova@suse.c | |om) | --- Comment #7 from Kristyna Streitova --- (In reply to Franck Bui from comment #6)

Anyway Kristyna, the process here doesn't look correct: it seems more a RFE than an issue to me.

And in such case it would be much better to discuss this with upstream (systemd-devel@lists.freedesktop.org) so we can figure out if the feature is really missing in systemd or if it is/should-be part of another/new project.

Would it be possible that you can discuss this issue with the upstream as a systemd package maintainer? Thank you!

I don't think such discussion belongs to downstream.

And I'm really not convinced that supporting the solution brought by Arch is the way to go.

I agree it's rather a hack than a nice solution. It's definitely better to have a proper and supported solution from the upstream. Or at least a clear statement that we should forget about cron MAILTO behaviour in timers and use a little bit different approach (e.g. systemd-denotify). -- You are receiving this mail because: You are on the CC list for the bug.