Bug#633858: -v not as safe as it sounds

[Dmitry Bogatov]

control: tags -1 +confirmed

[2019-02-01 09:45] Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups at NTLWorld.COM>
> Jesse Smith:
> > The -v command only turns on verbose messages,
>
> The manual page does not say this.  It says "Write out what is currently 
> going on", which can, as this bug proves, be read as writing out a 
> status report of what is currently the case for service configuration.  
> This is not good writing.  It makes the reader ask "What is currently 
> going on /where/?" and "What precisely do you mean by /going on/?".  
> Whereas "turn on verbose messages, showing what actions insserv is 
> taking" does not inspire such questions.
>
> I suggest putting this explanation of yours into the manual.

I agree with this suggestion. While it is common sense, that -v
increases verbosity, while -n is about `dry run', being more unambiguous
in manpage would be nice.
-- 
        Note, that I send and fetch email in batch, once every 24 hours.
                 If matter is urgent, try https://t.me/kaction
                                                                             --