Comment 21 for bug 1157643

The problem is the key (in my case: "net.ipv4.conf.default.rp_filter" or "net.ipv4.conf.all.rp_filter"). It does not matter whether it is set to 0 or 1, the problem is the definition (in my case: /etc/sysctl.d/10-network-security.conf). If the key is set, the start of the "procps" service fails. It worked fine before installing the update, i.e. the procps update is broken.