Bug 1217959
| Summary: | journal logging support | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | maxim.suraev |
| Component: | libguestfs | Assignee: | Richard W.M. Jones <rjones> |
| Status: | NEW --- | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | ptoscano |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
maxim.suraev
2015-05-03 12:03:16 UTC
I'm a bit confused about this bug. Libguestfs supplies access to journald APIs already, and we have tools like virt-log to provide access to logs from guests (whether or not they use systemd journal or something else): http://libguestfs.org/guestfs.3.html#systemd-journal-files http://libguestfs.org/virt-log.1.html Libguestfs debugging (a different thing from the above) goes to stderr by default unless you install your own handlers, in which case you can send it anywhere. However this is something that applications linking to libguestfs would do, not libguestfs itself. http://libguestfs.org/guestfs.3.html#example:-capturing-log-messages As far as I know, libguestfs does not require logrotate. It could be an indirect dependency of the appliance. |