Making rc.local work on F20.

[Derrik Walker v2.0]

There has been discussion of what it takes to make rc.local work. It 
seems that some people are struggling with it.

There are a couple of important details, but for the most part, It's 
almost trivial, as long as your not missing the important parts.

First thing I did was:

# cd/etc
# echo '$!/bin/bash' > /rc.d/rc.local
# ln -s rc.d/rc.local rc.local # because certain things are just burned 
into my brain.
# chmod 755 rc.d/rc.local
# vi /etc/rc.local

Setting the file permissions and making sure '#!/bin/bash' at the top 
are VERY important.

So, if you are poking around on my system:

# ls -l /etc/rc.local
lrwxrwxrwx. 1 root root 13 Mar  1 13:47 /etc/rc.local -> rc.d/rc.local

# ls -l /etc/rc.d/rc.local
-rwxr-xr-x. 1 root root 376 Jun 26 09:05 /etc/rc.d/rc.local

# cat /etc/rc.local
#!/bin/bash

# Fix the scheduler of the SSD
#
# changed to use deadline per benchmarks:
# http://www.phoronix.com/scan.php?item=linux_316_iosched&page=article
# 2014-06-26    dw2
#
# echo noop > /sys/block/sda/queue/scheduler
echo deadline > /sys/block/sda/queue/scheduler

#
# send an email on a (re)boot
#
echo $(hostname) booted on $(date) | mail -s "$(hostname) boot" root

And as you can see, it works:

# systemctl status rc-local
rc-local.service - /etc/rc.d/rc.local Compatibility
    Loaded: loaded (/usr/lib/systemd/system/rc-local.service; static)
    Active: active (exited) since Tue 2014-10-07 23:20:39 EDT; 2 weeks 3 
days ago
  Main PID: 1036 (code=exited, status=0/SUCCESS)
    CGroup: /system.slice/rc-local.service

Oct 07 23:20:39 tesla systemd[1]: Started /etc/rc.d/rc.local Compatibility.
Oct 07 23:20:39 tesla sendmail[1036]: s983Kd5f001036: from=root, 
size=244, ...st
Oct 07 23:20:40 tesla sendmail[1036]: s983Kd5f001036: to=root, 
ctladdr=root...y)
Hint: Some lines were ellipsized, use -l to show in full.


# cat /sys/block/sda/queue/scheduler
noop [deadline] cfq

That's it.

Really, all you need is to create a proper shell script in 
/etc/rc.d/rc.local with the correct permissions and it should work.

-- 
-- Derrik

Derrik Walker v2.0, RHCE
dwalker(a)doomd.net

"Those UNIX guys, they think weird!" -- John C. Dvorak

[Tim]

On Sat, 2014-10-25 at 21:25 -0400, Derrik Walker v2.0 wrote:
>  First thing I did was:
>   
>  # cd/etc 
Typo, there, too.  I think this is what you meant, getting rid of all
the typos into one list, together, and inserting what you probably did
do first:

su -

cd /etc
echo '#!/bin/bash' > rc.d/rc.local
ln -s rc.d/rc.local rc.local
chmod 755 rc.d/rc.local
vi /etc/rc.local

It's actually a rather neat example of the command line way of doing
things, as a person can play cut and paste with this, and replicate it,
themselves, with the minimum of fuss (with only the first and last
things needing interaction, the middle lines could be cut and pasted as
one blob).  Compared to the GUI alternative, with a long winded list of
instructions that the person would have to act out, and the list would
be different depending on which desktop GUI you were using.

-- 
tim@localhost ~]$ uname -rsvp

Linux 3.16.6-200.fc20.i686 #1 SMP Wed Oct 15 13:48:38 UTC 2014 i686

All mail to my mailbox is automatically deleted, there is no point trying
to privately email me, I will only read messages posted to the public lists.

George Orwell's '1984' was supposed to be a warning against tyranny, not
a set of instructions for supposedly democratic governments.

[Derrik Walker v2.0]

On 10/25/2014 10:24 PM, Kevin Cummings wrote:
>  On 10/25/2014 09:25 PM, Derrik Walker v2.0 wrote:
> > First thing I did was:
> >
> > # cd/etc
> > # echo '$!/bin/bash' > /rc.d/rc.local
>  Warning, you should echo a line beginning with #!, not $!
>
>  Second, you should echo it to rc.d/rc.local (note the missing / at the
>  beginning of the path), otherwise you might be able to find it.
>
>  Also, don't do this is you already have data in /etc/rc.d/rc.local as
>  that line will replace the contents of the file with the one line.
>
>  The rest of Derrik's advice is spot on (any further typos not
>  withstanding) as it matches the working rc.local file on my F19 server.
>  
Kevin is of course correct.  Sorry about the typos.

I guess I probably should have also added that I did that with a new 
install of the OS ( when I put my SSD in to be precise ), so 
/etc/rc.d/rc.local didn't yet exist.

-- 
-- Derrik

Derrik Walker v2.0, RHCE
dwalker(a)doomd.net

"Those UNIX guys, they think weird!" -- John C. Dvorak

[Kevin Cummings]

On 10/25/2014 09:25 PM, Derrik Walker v2.0 wrote:
>  First thing I did was:
>  
>  # cd/etc
>  # echo '$!/bin/bash' > /rc.d/rc.local 
Warning, you should echo a line beginning with #!, not $!

Second, you should echo it to rc.d/rc.local (note the missing / at the
beginning of the path), otherwise you might be able to find it.

Also, don't do this is you already have data in /etc/rc.d/rc.local as
that line will replace the contents of the file with the one line.

The rest of Derrik's advice is spot on (any further typos not
withstanding) as it matches the working rc.local file on my F19 server.

-- 
Kevin J. Cummings
kjchome(a)verizon.net
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
Registered Linux User #1232 (http://www.linuxcounter.net/)

[Derrik Walker v2.0]

On 10/26/2014 02:19 AM, Tim wrote:
>  On Sat, 2014-10-25 at 21:25 -0400, Derrik Walker v2.0 wrote:
> > First thing I did was:
> >   
> > # cd/etc
>  Typo, there, too.  I think this is what you meant, getting rid of all
>  the typos into one list, together, and inserting what you probably did
>  do first:
>
>  su -
>
>  cd /etc
>  echo '#!/bin/bash' > rc.d/rc.local
>  ln -s rc.d/rc.local rc.local
>  chmod 755 rc.d/rc.local
>  vi /etc/rc.local
>
>  It's actually a rather neat example of the command line way of doing
>  things, as a person can play cut and paste with this, and replicate it,
>  themselves, with the minimum of fuss (with only the first and last
>  things needing interaction, the middle lines could be cut and pasted as
>  one blob).  Compared to the GUI alternative, with a long winded list of
>  instructions that the person would have to act out, and the list would
>  be different depending on which desktop GUI you were using.
>  
Obviously, I didn't copy and paste ( just typed from memory ).

Anyway, yea, GUI's are nice for somethings like image/video/audio 
editing, but for system work and administration, a good UNIX CLI always 
wins.

-- 
-- Derrik

Derrik Walker v2.0, RHCE
dwalker(a)doomd.net

"Those UNIX guys, they think weird!" -- John C. Dvorak