busctl: monitor - only start printing messages once we have become a monitor (#5931)
authorTom Gundersen <teg@jklm.no>
Thu, 11 May 2017 13:56:55 +0000 (15:56 +0200)
committerLennart Poettering <lennart@poettering.net>
Thu, 11 May 2017 13:56:55 +0000 (15:56 +0200)
commitf5938e8ff3cf5b6fadd6b440b3b10fc0e5a64733
tree9ffdda73f2d52587b37bd8cd366e9c6827726f09
parent52511fae7befd356de8ef824d8302aaef47dd849
busctl: monitor - only start printing messages once we have become a monitor (#5931)

A connection becomes a monitor the moment it loses its unique name, so any
messages received before that should not be dumped to the console.

Currently, we print NameAcquired and NameLost for the unique name of the
peer that becomes the monitor, simply discard all messages until we
receive our NameLost signal.
src/busctl/busctl.c