'service procps start' does nothing; outdated README

Bug #1719159 reported by Marius Gedminas
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
procps (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

/etc/sysctl.d/README says

    After making any changes, please run "service procps start" (or, from
    a Debian package maintainer script "invoke-rc.d procps start").

however running this command does absolutely nothing on Ubuntu 17.04 (and,
presumably, any other Ubuntu version since systemd became the main init
system).

To actually get your changes written into /proc/sys, you have to do

    service procps reload

Can you please update the README?

(This is similar to bug 1332362, but I think that one was Upstart's fault.)

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: procps 2:3.3.12-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Sep 24 11:26:45 2017
InstallationDate: Installed on 2016-09-10 (379 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
SourcePackage: procps
UpgradeStatus: Upgraded to zesty on 2017-04-14 (163 days ago)

Revision history for this message
Marius Gedminas (mgedmin) wrote :
tags: removed: wayland-session
Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :

On Bionic, the README file was upgraded on 10Jul2016; a bit old !!!

tags: removed: zesty
tags: added: artful bionic
summary: - 'service procps start' does nothing
+ 'service procps start' does nothing; outdated README
Revision history for this message
dino99 (9d9) wrote :

Both Ubuntu & Debian still use that old version; even if procps is still continously upgraded.

https://gitlab.com/procps-ng/procps

Please upgrade the ubuntu archive

tags: added: upgrade-software-version
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in procps (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package procps - 2:3.3.15-2ubuntu1

---------------
procps (2:3.3.15-2ubuntu1) cosmic; urgency=medium

  * Merge from Debian unstable. Remaining changes:
    - debian/sysctl.d (Ubuntu-specific):
      + 10-console-messages.conf: stop low-level kernel messages on console.
      + 10-kernel-hardening.conf: add the kptr_restrict setting
      + 10-keyboard.conf.powerpc: mouse button emulation on PowerPC.
      + 10-ipv6-privacy.conf: add a file to sysctl.d to apply the defaults
        for IPv6 privacy extensions for interfaces. (LP: #176125, #841353)
      + 10-link-restrictions.conf: even though the Ubuntu
        kernel is built with these defaults in place, we want to make sure
        that people running stock kernels don't miss out.
      + 10-magic-sysrq.conf: Disable most magic sysrq by default, allowing
        critical sync, remount, reboot functions. (LP: #194676, LP: #1025467)
      + 10-network-security.conf: enable rp_filter.
      + 10-ptrace.conf: describe new PTRACE setting.
      + 10-zeropage.conf: safe mmap_min_addr value for graceful fall-back.
        for armhf, and arm64.
      + 10-qemu.conf.s390x for qemu.
      + README: describe how this directory is supposed to work.
    - debian/rules: Fix cross build
    - ignore_eaccess.patch: If we get eaccess when opening a sysctl file for
      writing, don't error out. Otherwise package upgrades can fail,
      especially in containers.
    - ignore_erofs.patch: Same as ignore_eaccess but for the case where
      part of /proc is read/only.

procps (2:3.3.15-2) unstable; urgency=medium

  * Fix link in libprocps-dev Closes: 900239
  * Fix typo in license Closes: #899346

 -- Balint Reczey <email address hidden> Tue, 05 Jun 2018 11:20:00 -0700

Changed in procps (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.