Additionally, the ifdown/ifup method does not load certain changes (e.g.
IP address) properly, and often breaks networking when such changes are
made.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301
The command in comment #8 *should* do this in a single exec resource:
sudo ifdown --exclude=lo -a && sudo ifup --exclude=lo -a
However, I have found this does not actually work either for any
significant config change (e.g. IP address change, gateway change). In
fact, the command above frequentl
#8 is a good analysis... this change breaks manually running logrotate
with a specific file as argument. It doesn't seem to affect automatic
rotation due to the su line in /etc/logrotate.conf.
Seems that making root:syslog the default for all logrotate scripts
would fix this behavior, as would r
I second rgtaylor's request. This additionally has great impact on
automated build scripts & systems (in my case, Foreman/puppet) which
need a way to make networking changes (such as new IP address) & apply
those changes, often on systems for which console access is (at best)
inconvenient due to l
I also confirm this issue for Trusty with v. 4.1.6. It seems that the
order in which the gids are evaluated is crtical, in that NO groups
(including those with valid gids) are resolved after the first incidence
of a group with missing gid, and therefore group memberships after this
are simply miss
The referenced fix has to do with the clarity of an error message, not
the startup performance of the package. Based on comments above and my
own testing, the fix does not affect the subject of this bug report.
Recommend this bug be set to Open or at least Won't Fix.
--
You received this bug not
Apologies if it is improper to comment here... just wanted to mention
that I was also affected by this bug. I worked around it by editing the
/etc/usplash.conf file (as directed by the Debugging Usplash wiki link
above) and changing the resolution from the default (1920x1080, which is
the correct
