i isntall the fedora 16 but can't find the rc.local file

i create the rc.local in /etc/rc.d/

but the fedora start up can't run rc.local.

how to fix this problem.

Thx

Make sure the first line is #! /bin/sh and the file is executable.

added #! /bin/sh
and set the chmod 755 still can't start up

I think Fedora wants the path to be /etc/rc.local, not /etc/rc.d/rc.local.

http://www.fedorafaq.org/basics/#startonboot

On my Fedora 14, it's in /etc/rc.d/rc.local with a link from /etc/rc.local. But surely this is part of the Sys V init system? It might be ignored because Fedora 16 is using startd or whatever it's called.

I test the rc.local can startup now

but the command can work

rc.local
----------------------------------------------------------------
#!/bin/sh

route add -net 192.168.0.0 netmask 255.255.255.0 gw 192.168.1.254

date > test.txt
-----------------------------------------------------------------

the route add this line don't work

Thanks, David McCann. I heard that Fedora was playing with the init process in v. 16, but I haven't played with it yet.

First, bear in mind that the rc.local script is not strictly a *nix rc type of service start up command. What I am saying here is that depending on the run-level, services should be started up under the rc.x directories. So, the solution I have used is to create a legitimate service under the /etc/init.d directory and to start the service automatically using chkconfig. For example, I wanted to customize my resolv.conf file. So, the solution went as follows:

I created a bash file called /etc/init.d/res:


#!/bin/bash
#
#chkconfig: 345 82 20
#description: alter resolv.conf
#
RETVAL=0

case "$1" in
"start")
# start daemon
echo "Altering the resolv.conf file"
RETVAL=$?
\cp -f /opt/resolv.conf /etc/resolv.conf
;;

*)
echo "Usage: $0 {start}"
exit 1
;;
esac


Next, I turned the bash program into a service:

# chmod +x /etc/init.d/res
# chkconfig --add res
# chkconfig --list | grep res
# chkconfig res on
# service res start

Finally, I verified the operation of the bash program, after the boot-up. Voila, fixed!

One more thing.....Fedora may be for "tinkering" as a Beta operating system, but, I would guess that some of the persons on this forum are supposed "IT guys". Please be aware that some of these frameworks were put in the original Unix System V OS.

Also this should work:

rc.local's place is /etc/rc.d/rc.local
rc.local should be executable (mode 755).

Create a symlink in /etc/systemd/system/multi-user.target.wants/ to tell Fedora to execute rc-local service (which executes rc.local):
ln -s /lib/systemd/system/rc-local.service /etc/systemd/system/multi-user.target.wants/rc-local.service


Check with systemctl status rc-local.service if rc-local has been executed on boot or resume.