Bug 1577842
Summary: | RFE: make UNIX socket path configurable for virtlockd/virtlogd | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | mathieu.tarral |
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
Status: | NEW --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | berrange, libvirt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
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
mathieu.tarral
2018-05-14 09:10:10 UTC
Err, if you've set configure --prefix to install into $HOME/user, then /etc/libvirt/libvirtd.conf is no longer the right path. Unless you set an explicit --sysconfdir=/etc arg to configure, the right config file is going to be $HOME/usr/etc/libvirt/libvirtd.conf Hi Daniel, There is a word missing here in my initial report: > If you edit /etc/libvirt/libvirtd.conf to set > unix_sock_dir = "/var/run/libvirt", should be If you edit $HOME/usr/etc/libvirt/libvirtd.conf to set unix_sock_dir = "/var/run/libvirt", As you said: > the right config file is going to be $HOME/usr/etc/libvirt/libvirtd.conf yes, and the bug is that virLogManagerDaemonPath() doesn't read this config file to get the unix_sock_dir location. Is this more clear ? Thanks. Note that the libvirtd.conf file is only for configuring libvirtd daemon - it has no impact on virtlogd or virtlockd, which have their own configuration files. Now, neither virtlogd.conf or virtlockd.conf support changing unix_sock_dir right now, so that would be an RFE. If we make those paths configurable, we'll also need another config file option to set the path for the client to use, as those config files are both for the server side. |