-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instead of our logging use syslog or even journal #92
Comments
By the way if you have some questions about systemd integration or potential features (socket activation pops up in my mind) feel free to contact me. |
So if I understand this correctly, the journal is suitable for the server side app because it will probably start on bootup as a daemon and the logging might be useful. But is the journal really usable for client side? The client app will run only for a short time and not much logging is actually needed... So the question is, should we use journal on server and syslog on client? |
Well there is no difference. If you use syslog api, the messages will end up in journal anyway. |
Ok thanks. One more question if you don't mind. I'm not that much familiar with systemd usage so I was wondering about the first point where you say "make sure that your service is wrapped by systemd unit". I'm not entirely sure what that means :( |
That is only related to the server part. Basically it means, have an unit-file and start it through systemd :-) |
Ok thanks a lot :) |
In my opinion, it is very important to leave the trace in system log (or other well-known location) that package set on the machine changed. When using yum admin can later consult output of |
Instead of ssds logging function use syslog or even journal.
@lnykryn: Can you please journalctl command for getting logs? How can we get ssds logs from journal?
The text was updated successfully, but these errors were encountered: