On Wed, Oct 07, 2009 at 03:34:38PM -0400, Amy Griffis wrote:
Daniel P. Berrange wrote: [Tue Oct 06 2009, 05:00:55AM EDT]
Having looked at the wway the next patch uses these, I think it'd be
nicer to change the contract to just be
extern char *virLogGetFilters(void);
Daniel P. Berrange wrote: [Tue Oct 06 2009, 05:00:55AM EDT]
Having looked at the wway the next patch uses these, I think it'd be
nicer to change the contract to just be
extern char *virLogGetFilters(void);
extern char *virLogGetOutputs(void);
Heh, that's how I wrote it
On Wed, Oct 07, 2009 at 03:34:38PM -0400, Amy Griffis wrote:
Daniel P. Berrange wrote: [Tue Oct 06 2009, 05:00:55AM EDT]
Having looked at the wway the next patch uses these, I think it'd be
nicer to change the contract to just be
extern char *virLogGetFilters(void);
On Sun, Oct 04, 2009 at 03:28:46PM -0400, Amy Griffis wrote:
When configuring logging settings, keep more information about the
output destination. Add accessors to retrieve the filter and output
settings in the original string form; this to be used to set up
environment for a child process
Daniel P. Berrange wrote: [Mon Oct 05 2009, 08:51:00AM EDT]
On Sun, Oct 04, 2009 at 03:28:46PM -0400, Amy Griffis wrote:
When configuring logging settings, keep more information about the
output destination. Add accessors to retrieve the filter and output
settings in the original string
When configuring logging settings, keep more information about the
output destination. Add accessors to retrieve the filter and output
settings in the original string form; this to be used to set up
environment for a child process that also logs. Open output files
O_APPEND so child can also write
