also sprach Axel Beckert <a...@debian.org> [2016-09-22 10:56 +0200]:
> > Please note how first pre-/postdisconnect are run. Why is that? The
> > cable had long before been disconnected, so while this is not a big
> > deal, it seems wrong.
> 
> Well, I'd call it debatable. I also see reasons for this behaviour.

The pre-/postdisconnect scripts should be called upon disconnection,
which was yesterday. And they were called. Now they were called
*again* upon connection, and I find it hard to find a rationale for
this to be debatable. ;)

> > What's worse though is that the pre-/postdisconnect scripts are run
> > *again* after preconnect and before postconnect, which can break
> > some applications, e.g. enabled ipv6 autoconf in preconnect and
> > turning it off in postdisconnect.
> 
> Thanks for this very precise bug report. The latter behaviour indeed
> sounds wrong and may explain some other reported or seen issues. Will
> have a look at it.

Thank you!

-- 
 .''`.   martin f. krafft <madduck@d.o> @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
*** important disclaimer:
by sending an email to any address, that will eventually cause it to
end up in my inbox without much interaction, you are agreeing that:
 
  - i am by definition, "the intended recipient"
  - all information in the email is mine to do with as i see fit and
    make such financial profit, political mileage, or good joke as it
    lends itself to. in particular, i may quote it on usenet.
  - i may take the contents as representing the views of your company.
  - this overrides any disclaimer or statement of confidentiality that
    may be included on your message.

Attachment: digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Reply via email to