rc.local not executing commands

Petter Adsen petter at synth.no
Thu Nov 5 14:47:12 UTC 2015


On Thu, 5 Nov 2015 14:24:17 +0000
R Kimber <richardkimber at btinternet.com> wrote:

> On Thu, 5 Nov 2015 14:57:40 +0100
> silver.bullet at zoho.com wrote:
> 
> > You did not mention what Ubuntu you are using, resp. what startup
> > process your Ubuntu does use.  
> 
> Sorry it's 15.04 ubuntu mate
> 
> > If you're using systemd, then use an unit, to
> > 
> >   /lib/systemd/system/
> > 
> > write a file named
> > 
> >   cpu_freq_scaling.service
> > 
> > with this content:
> > 
> >   [Unit]
> >   Description=cpu_freq_scaling
> > 
> >   [Service]
> >   Type=oneshot
> >   ExecStart=/usr/bin/cpufreq-set -u 4.0Ghz
> >   RemainAfterExit=true
> > 
> >   [Install]
> >   WantedBy=multi-user.target
> > 
> > then run
> > 
> >   sudo -i
> >   systemctl start cpu_freq_scaling
> >   systemctl enable cpu_freq_scaling
> > 
> > Regards,
> > Ralf  
> 
> Thanks.  I can see that there are various ways one might have the
> command executed.  But rc.local ought to work surely? It says:
> 
> # This script is executed at the end of each multiuser runlevel.
> 
> It's really irritating when a simple method of doing something doesn't
> work. Is it a bug?

No, rc.local isn't enabled by default. 'sudo systemctl enable
rc.local' will enable it.

Petter

-- 
"I'm ionized"
"Are you sure?"
"I'm positive."



More information about the ubuntu-users mailing list