Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been trying to get some settings in /etc/sysctl.conf to take effect upon rebooting. So, I did the following as the root user on this node running Ubuntu 12.04 LTS 64bit

# service procps status
procps stop/waiting
# service procps start
procps stop/waiting

No matter how I tried. The /etc/init/procps is stock as shown below. I have not touched it (not familiar with upstart yet).

# procps - set sysctls from /etc/sysctl.conf
# This task sets kernel sysctl variables from /etc/sysctl.conf and
# /etc/sysctl.d

description     "set sysctls from /etc/sysctl.conf"


start on virtual-filesystems or static-network-up

    cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sysctl -e -p -
end script

I would appreciate it very much for any hints about how to start this upstart job.

Up to now, I always have to manually issue /sbin/sysctl -p /etc/sysctl.conf. It gets old really fast...


-- Zack

share|improve this question

The procps service really isn't a long-running daemon. service procps start just invokes the script in /etc/init/procps, which causes all the contents of /etc/sysctl.d/*.conf and /etc/sysctl.conf to be piped to sysctl -e -p -.

So, the act of running service procps start is pretty much the same as what you are manually doing, and should already be applying at boot, assuming your procps upstart job is configured to run.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.