Control: affects -1 - ethtool
I believe ethtool's scripts always return 0 if successful.
Ben.
--
Ben Hutchings
All the simple programs have been written, and all the good names
taken.
signature.asc
Description: This is a digitally signed message part
Control: affects 661591 - ifmetric
I checked that the ifmetric if-up script exits 0 on success and 1 on error.
--
Kind regards,
Michael Shuler
signature.asc
Description: OpenPGP digital signature
affects #661591 - ifupdown-scripts-zg2
thanks
ifupdown-scripts-zg2 cleanly exits 1 with an error, and exits 0 if
everything is fine.
Greetings
Marc
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
affects 661591 - tinc
thanks
I made a minor change in 1.0.19-1 to ignore errors when poking tinc in response
to other interfaces being brought up. Other than that, I cannot see anything
wrong.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen g...@debian.org
signature.asc
Andrew,
why do you think bug #661591 is not fixed?
Was it this missleading changelog message:
Ifupdown hooks are not installed by default anymore.
Or do you have other reasons?
Masqmail-0.3.4-1 doesn't install ifupdown hooks at all. Actually, it
does not at all interface ifupdown
Hello,
On Sat, 23 Jun 2012 12:30:09 +0200
markus schnalke mei...@marmaro.de wrote:
Or do you have other reasons?
Obviously, because it wasn't filed against masqmail.
--
WBR, Andrew
signature.asc
Description: PGP signature
affects 661591 - masqmail
thanks
[2012-06-23 20:44] Andrew Shadura bugzi...@tut.by
On Sat, 23 Jun 2012 12:30:09 +0200
markus schnalke mei...@marmaro.de wrote:
Or do you have other reasons?
Obviously, because it wasn't filed against masqmail.
Oh, now I see. Seems as if I am not enough
Package: general
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Starting with the last beta, ifupdown calls run-parts for if-*.d scripts
with --exit-on-error, so if the script fails, interface isn't marked as
configured (see #547587).
However, it's been reported that some
Hi Andrew,
On Tue, Feb 28, 2012 at 11:24:43AM +0100, Andrew O. Shadura wrote:
Starting with the last beta, ifupdown calls run-parts for if-*.d scripts
with --exit-on-error, so if the script fails, interface isn't marked as
configured (see #547587).
However, it's been reported that some
reassign 661591 ifupdown
thanks
Hi,
just from what I've read in those two replies to this bug yet, I think I agree
that this change should be reverted.
And if you really want/need/do this change which needs changes in 30 (or so)
other packages, then please file 30 bugs against those package
Hello,
On Tue, 28 Feb 2012 22:37:29 +0100
Holger Levsen hol...@layer-acht.org wrote:
just from what I've read in those two replies to this bug yet, I
think I agree that this change should be reverted.
And if you really want/need/do this change which needs changes in 30
(or so) other
On Tue, Feb 28, 2012 at 09:09:22PM +0100, Andrew Shadura wrote:
On Tue, 28 Feb 2012 11:27:37 -0800
Steve Langasek vor...@debian.org wrote:
However, it's been reported that some scripts return wrong exit
codes sometimes, causing failure during network configuration.
My doubt here is:
Hello,
On Tue, 28 Feb 2012 14:27:15 -0800
Steve Langasek vor...@debian.org wrote:
When failure to execute a hook leads to interface being
non-operational.
Yes, that's probably a reasonable threshold. What should packages
like miredo and wide-dhcpv6-client do? Both of these hooks have to
Hi Andrew,
On Dienstag, 28. Februar 2012, Andrew Shadura wrote:
Obviously I want this process to happen, but as a start a bug must be
filed, so discussion can start, no? I understand this exactly this way.
Yes, use this bug to track all the other bugs you (and others) will be filing.
then use
14 matches
Mail list logo
