Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
lede-mikrotik
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
External wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Johannes Rudolph
lede-mikrotik
Commits
00818780
Commit
00818780
authored
18 years ago
by
Felix Fietkau
Browse files
Options
Downloads
Patches
Plain Diff
add some documentation for the init scripts
SVN-Revision: 5140
parent
75c1f290
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/init-scripts.tex
+61
-0
61 additions, 0 deletions
docs/init-scripts.tex
docs/openwrt.tex
+1
-0
1 addition, 0 deletions
docs/openwrt.tex
with
62 additions
and
0 deletions
docs/init-scripts.tex
0 → 100644
+
61
−
0
View file @
00818780
Because OpenWrt uses its own init script system, all init scripts must be installed
as
\texttt
{
/etc/init.d/
\textit
{
name
}}
use
\texttt
{
/etc/rc.common
}
as a wrapper.
Example:
\texttt
{
/etc/init.d/httpd
}
\begin{Verbatim}
#!/bin/sh /etc/rc.common
# Copyright (C) 2006 OpenWrt.org
START=50
start()
{
[ -d /www ]
&&
httpd -p 80 -h /www -r OpenWrt
}
stop()
{
killall httpd
}
\end{Verbatim}
as you can see, the script does not actually parse the command line arguments itself.
This is done by the wrapper script
\texttt
{
/etc/rc.common
}
.
\texttt
{
start()
}
and
\texttt
{
stop()
}
are the basic functions, which almost any init
script should provide.
\texttt
{
start()
}
is called when the user runs
\texttt
{
/etc/init.d/httpd start
}
or (if the script is enabled and does not override this behavior) at system boot time.
Enabling and disabling init scripts is done by running
\texttt
{
/etc/init.d/
\textit
{
name
}
start
}
or
\texttt
{
/etc/init.d/
\textit
{
name
}
stop
}
. This creates or removes symbolic links to the
init script in
\texttt
{
/etc/rc.d
}
, which is processed by
\texttt
{
/etc/init.d/rcS
}
at boot time.
The order in which these scripts are run is defined in the variable
\texttt
{
START
}
in the init
script, which is optional and defaults to
\texttt
{
50
}
. Changing it requires running
\texttt
{
/etc/init.d/
\textit
{
name
}
enable
}
again.
You can also override these standard init script functions:
\begin{itemize}
\item
\texttt
{
boot()
}
\\
Commands to be run at boot time. Defaults to
\texttt
{
start()
}
\item
\texttt
{
restart()
}
\\
Restart your service. Defaults to
\texttt
{
stop(); start()
}
\item
\texttt
{
reload()
}
\\
Reload the configuration files for your service. Defaults to
\texttt
{
restart()
}
\end{itemize}
You can also add custom commands by creating the appropriate functions and referencing them
in the
\texttt
{
EXTRA
\_
COMMANDS
}
variable. Helptext is added in
\texttt
{
EXTRA
\_
HELP
}
.
Example:
\begin{Verbatim}
status()
{
# print the status info
}
EXTRA
_
COMMANDS="status"
EXTRA
_
HELP=" status Print the status of the service"
\end{Verbatim}
This diff is collapsed.
Click to expand it.
docs/openwrt.tex
+
1
−
0
View file @
00818780
...
...
@@ -25,6 +25,7 @@
\subsection
{
Hotplug
}
\subsection
{
Init scripts
}
\include
{
init-scripts
}
\subsection
{
Network scripts
}
\include
{
network-scripts
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment