On 03/26/2018 10:44 AM, Peter Krempa wrote:
> On Mon, Mar 26, 2018 at 09:49:08 +0200, Peter Krempa wrote:
>> On Mon, Mar 26, 2018 at 07:16:42 +0200, Michal Privoznik wrote:
>>> Unless overridden, libdevmapper logs all messages to stderr.
>>> Therefore if something goes wrong in
On Mon, Mar 26, 2018 at 10:16:54 +0200, Michal Privoznik wrote:
> On 03/26/2018 09:49 AM, Peter Krempa wrote:
> > On Mon, Mar 26, 2018 at 07:16:42 +0200, Michal Privoznik wrote:
> >> Unless overridden, libdevmapper logs all messages to stderr.
> >> Therefore if something goes wrong in
On Mon, Mar 26, 2018 at 09:49:08 +0200, Peter Krempa wrote:
> On Mon, Mar 26, 2018 at 07:16:42 +0200, Michal Privoznik wrote:
> > Unless overridden, libdevmapper logs all messages to stderr.
> > Therefore if something goes wrong in storage_backend_mpath.c or
> > parthelper.c we don't honour user
On 03/26/2018 09:49 AM, Peter Krempa wrote:
> On Mon, Mar 26, 2018 at 07:16:42 +0200, Michal Privoznik wrote:
>> Unless overridden, libdevmapper logs all messages to stderr.
>> Therefore if something goes wrong in storage_backend_mpath.c or
>> parthelper.c we don't honour user set logging targets.
On Mon, Mar 26, 2018 at 07:16:42 +0200, Michal Privoznik wrote:
> Unless overridden, libdevmapper logs all messages to stderr.
> Therefore if something goes wrong in storage_backend_mpath.c or
> parthelper.c we don't honour user set logging targets.
>
> Signed-off-by: Michal Privoznik
Unless overridden, libdevmapper logs all messages to stderr.
Therefore if something goes wrong in storage_backend_mpath.c or
parthelper.c we don't honour user set logging targets.
Signed-off-by: Michal Privoznik
---
src/util/virlog.c | 23 +++
1 file