Alex Vandiver <alexmv@xxxxxxxxxxx> writes:
> The only current uses of this tool are in tests, which only examine
> the first ("no fsmonitor" / "fsmonitor last update ...") line. I find
> it useful as a brief summary view of the fsmonitor bits, but I suppose
> I'd also be happy with just presence/absence and a count of set/unset
> bits.
>
> Barring objections from Dscho or Ben, I'll reroll with a version that
> shows something like:
>
> fsmonitor last update 1513821151547101894 (5 seconds ago)
> 5 files valid / 10 files invalid
As I agree that this is test/debug only, I do not care too deeply
either way, as long as it does not end with an incomplete line ;-)
