freebsd at edvax.de
Sat Jan 30 11:00:06 UTC 2016
On Fri, 29 Jan 2016 16:35:07 -0600 (CST), Valeri Galtsev wrote:
> Dear Experts,
> How does one create "epoligue" script in FreeBSD. By "epoligue" script
> script I mean here the script that is executed after everything described
> in /etc/rc.conf is done (services started, interfaces initialized etc.). I
> tried to follow RTFM advise, but it looks like I'm too stupid to be able
> to find leads. I tried to put what I need into /etc/rc.conf.local, and
> what I put there is executed, but not after everything in /etc/rc.conf is
Note: /etc/rc.conf and /etc/rc.conf.local are configuration files.
Even though they are technically shell scripts that are being sourced
by the scripts that do the "real action", they usually just contain
variable assignments, comments, and empty lines.
But there are two mechanisms that might work for you. You have to
decide which one you want to use:
a) RC framework: rc.d
Create rc.d-style files for your programs and put them into a directory
where they can be sourced from: /usr/local/etc/rc.d is fine, but you
can also (ab)use the Solaris-ism /opt/etc/rc.d (which I do - for stuff
that is not managed by ports). In those files, you can exactly define
which requirements need to be fulfilled for a script to be run, and
which features they might activate for other scripts that depend on
See "man rc" and "man rcorder" for details.
b) rc.local and rc.shutdown.local
Those files, located in /etc, are "real" shell scripts that will be
executed "quite late", but not at the lastest possible point. Here
is an example:
Creating and/or trimming log files.
No core dumps found.
Additional ABI support: linux.
Clearing /tmp (X related).
Starting local daemons: activity. <--- /etc/rc.local runnung now!
Configuring syscons: keymap keyrate font8x16 font8x14 font8x8.
As you can see, there are other services started _after_ rc.local has
been run. This might cause a problem for you when you need those services
See from "man rc":
The rc.local script contains commands which are pertinent only
to a specific site. Typically, the /usr/local/etc/rc.d/ mechanism
is used instead of rc.local these days but if you want to use rc.local,
it is still supported. In this case, it should source /etc/rc.conf
and contain additional custom startup code for your system. The best
way to handle rc.local, however, is to separate it out into rc.d/
style scripts and place them under /usr/local/etc/rc.d/. The rc.conf
file contains the global system configuration information referenced
by the startup scripts, while rc.conf.local contains the local system
configuration. See rc.conf(5) for more information.
So this might not be "stable".
c) /etc/rc hook
You can add your own stuff at the end of /etc/rc, in "full text" or
by calling a wrapper script, but this step is not advised. /etc/rc
will be subject to OS updating.
> I'm left clueless. As Linux refugee I have a feeling that this is doable
> without a hack, like making init script, and having "sleep ..." in it
> before payload. In Linux this is done using /etc/rc.d/rc.local which is
> executed _after_ everything else is done.
As you can see, an rc.d style mechanism will probably be the best
solution here, except you are fully sure that the time when rc.local
is run you will be provided with everything you need.
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
More information about the freebsd-questions