Re: [Xen-devel] [PATCH v2 6/7] libxenstat: honour XEN_RUN_DIR

2016-08-15 Thread Ian Jackson
Wei Liu writes ("Re: [PATCH v2 6/7] libxenstat: honour XEN_RUN_DIR"): > On Wed, Jul 20, 2016 at 03:40:56PM +0100, Ian Jackson wrote: > > Wei Liu writes ("[PATCH v2 6/7] libxenstat: honour XEN_RUN_DIR"): > > > Backport candidate. > > > > Thanks. Can you let me know when it's applied to staging ? >

Re: [Xen-devel] [PATCH v2 6/7] libxenstat: honour XEN_RUN_DIR

2016-07-20 Thread Wei Liu
On Wed, Jul 20, 2016 at 03:40:56PM +0100, Ian Jackson wrote: > Wei Liu writes ("[PATCH v2 6/7] libxenstat: honour XEN_RUN_DIR"): > > This is because libxl uses XEN_RUN_DIR to generate the socket path for > > libxenstat while libxenstat itself uses hard-coded path, which is not > > necessarily the s

Re: [Xen-devel] [PATCH v2 6/7] libxenstat: honour XEN_RUN_DIR

2016-07-20 Thread Ian Jackson
Wei Liu writes ("[PATCH v2 6/7] libxenstat: honour XEN_RUN_DIR"): > This is because libxl uses XEN_RUN_DIR to generate the socket path for > libxenstat while libxenstat itself uses hard-coded path, which is not > necessarily the same path as XEN_RUN_DIR. The default configuration > happened to wor

[Xen-devel] [PATCH v2 6/7] libxenstat: honour XEN_RUN_DIR

2016-07-11 Thread Wei Liu
This is because libxl uses XEN_RUN_DIR to generate the socket path for libxenstat while libxenstat itself uses hard-coded path, which is not necessarily the same path as XEN_RUN_DIR. The default configuration happened to work because XEN_RUN_DIR defaulted to /var/run/xen, which matched the hard-co