| 1 |
On 24.02.2015 17:01, Rich Freeman wrote: |
| 2 |
|
| 3 |
> Seems like there should be a systemd-users mailing list, actually. |
| 4 |
> This sort of situation is completely distro-agnostic. |
| 5 |
|
| 6 |
Yes! And systemd-devel ml is always kind of "they will laugh at me and |
| 7 |
say ugly things!" ;-) |
| 8 |
|
| 9 |
> You certainly could design such an application. If you do so I'd |
| 10 |
> consider pulling the journald logs in JSON format. I'd also see if |
| 11 |
> somebody actually has written a journald library/class/etc for your |
| 12 |
> language of choice - it seems like that is the sort of thing that is |
| 13 |
> likely to exist soon if not already. One of the goals journald (and |
| 14 |
> systemd) is to provide more of an API for services so that there is |
| 15 |
> less parsing of text files and communicating via signals/etc. I'm |
| 16 |
> sure with appropriate permissions a process could just obtain log |
| 17 |
> entries via dbus, and using cursors poll for new entries (or maybe |
| 18 |
> there is a push/stream mechanism). |
| 19 |
> |
| 20 |
> Really though it seems like the solution is a generic log monitor with |
| 21 |
> rules for such things, with the monitor utilizing the JSON data from |
| 22 |
> journald for richer metadata/efficiency/accuracy. |
| 23 |
|
| 24 |
Well, it might be a nice challenge to do so ... sure! |
| 25 |
|
| 26 |
The real world challenge is that I have to provide the postfix-logs for |
| 27 |
one domain on one server (so far) for one "admin" to browse through |
| 28 |
(without giving him ssh-access ... it's a noob ...) |
| 29 |
|
| 30 |
No overkill paid here. |
| 31 |
|
| 32 |
But maybe I ask on systemd-devel-ml ... |
| 33 |
|
| 34 |
Stefan |
Archives