27.09.2015 12:47, Felix Miata пишет:
Andrei Borzenkov composed on 2015-09-27 12:27 (UTC+0300):
Felix Miata composed
If it only happened on one installation I might imagine that possible, but this is a problem on all the at least half dozen installations I've installed systemd-210 on as followup to https://bugzilla.opensuse.org/show_bug.cgi?id=924488 and https://bugzilla.opensuse.org/show_bug.cgi?id=832220 . All such installations have had zypper up run on them many times since https://bugzilla.opensuse.org/show_bug.cgi?id=857031 was marked fixed 19 months ago.
Could you paste /usr/lib/systemd/system/network@.service?
# ll network@.service -rw-r--r-- 1 root root 280 Oct 29 2013 network@.service # rpm -qf ./network@.service sysconfig-network-0.81.6-1.1.i586
Where did you get it from? The latest patch for 13.1 is 0.81.5-30.1.
[Unit] Description=ifup managed network interface %i Requisite=network.service PartOf=network.service BindsTo=sys-subsystem-net-devices-%i.device IgnoreOnIsolate=yes
[Service] Type=forking RemainAfterExit=yes ExecStart=/sbin/ifup %i ExecStop=/sbin/ifdown %i SuccessExitStatus=12
Doesn't http://download.opensuse.org/repositories/home:/tsaupe:/branches:/openSUSE:/... include a good enough fix to include in updates?
The problem is not in systemd, but in services used to configure interfaces which are from openSUSE.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org