Summary: | "service network stop" doesn't bring down ifaces which actually has been brought up | ||
---|---|---|---|
Product: | Branch 4.1 | Reporter: | Ivan Zakharyaschev <imz> |
Component: | etcnet | Assignee: | Nobody's working on this, feel free to take it <nobody> |
Status: | CLOSED WONTFIX | QA Contact: | qa-4.1 <qa-4.1> |
Severity: | normal | ||
Priority: | P2 | CC: | pilot |
Version: | unspecified | ||
Hardware: | all | ||
OS: | Linux |
Description
Ivan Zakharyaschev
2008-12-31 19:22:12 MSK
Related reports: https://bugzilla.altlinux.org/show_bug.cgi?id=9683 (doesn't bring down an iface declared DISABLED (instead of my intention to stop the network)) https://bugzilla.altlinux.org/show_bug.cgi?id=16910 (doesn't bring down an iface after a change in the configuration which makes the iface unknown/disbaled) I think that a general rule could be assumed (such that most users will agree with it): if the intended state of a certain iface in the new state of the network is down (it is declared disabled in the new profile, or the whole network is brought down), then it must be brought down. An "exception"/different case might be the case when an iface is unknown in the new profile/configuration: then there is simply no intention stated about it, and it can be left up. В 4.1/branch исправления не будут вноситься уже технически (заглушена очередь на сборку), поэтому прошу ошибки, актуальные для sisyphus/p7/t7, перевесить на текущие ветки или сизиф. |