Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
6
66
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
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
Eric Vidal
66
Commits
5581246a
Commit
5581246a
authored
6 years ago
by
Eric Vidal
Browse files
Options
Downloads
Patches
Plain Diff
update 66-scandir.html page
parent
9f2bc0eb
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/66-scandir.html
+31
-29
31 additions, 29 deletions
doc/66-scandir.html
with
31 additions
and
29 deletions
doc/66-scandir.html
+
31
−
29
View file @
5581246a
...
...
@@ -49,7 +49,7 @@
<li>
<tt>
-b
</tt>
: create specific files for boot. Only root
user can use this option - see
"
.s6-svscan control directory"
section
.
user can use this option - see
<a
href=
"#svscanctld"
>
.s6-svscan control directory"
</a>
.
</li>
<li>
<tt>
-l
<em>
live
</em></tt>
: create the scandir at
<em>
live
</em>
. Default is
...
...
@@ -61,7 +61,7 @@
<li>
<tt>
-t
<em>
rescan
</em></tt>
: perform a scan every
<tt><em>
rescan
</em></tt>
milliseconds. If
<tt><em>
rescan
</em></tt>
is set to
0
(the default), automatic scans are never performed after
milliseconds. If
<tt><em>
rescan
</em></tt>
is set to
<tty>
0
</tty>
(the default), automatic scans are never performed after
the first one and s6-svscan will only detect new services by
issuing either
<tt><em>
66-scandir -s reload
</em></tt>
or
<tt><em><a
href=
"https://skarnet.org/software/s6/s6-svscanctl.html"
>
66-svscanctl -a
</a>
...
...
@@ -70,28 +70,28 @@
</li>
<li>
<tt>
-2
<em>
stage2.tini
</em></tt>
:
set
the command to
execute with configurable handlers when the scandir receive a signal.
An absolute path is expected. This option
s
is mandatory if passing
<em>
-b
</em>
<tt>
-2
<em>
stage2.tini
</em></tt>
:
make
the command to
execute
a script
with configurable handlers when the scandir receive
s
a signal.
An absolute path is expected. This option is mandatory if passing
<em>
-b
</em>
and cannot be used on its own. If not set, the default script at
<tt><em>
/etc/66/stage2.tini
</em></tt>
will be called.
Also,
66 tools
do not
provide
this
script
s
. It's the responsability
of the system administrator to
furnish
it.
None of the
66 tools
will
provide
such a
script. It's the responsability
of the system administrator to
provide
it.
</li>
<li>
<tt>
-3
<em>
stage3
</em></tt>
: script to execute when
the scandir is asked to be shut down. An absolute path is expected.
This option
s
is mandatory if passing
<em>
-b
</em>
and cannot be
This option is mandatory if passing
<em>
-b
</em>
and cannot be
used on its own. If not set, the default script at
<tt><em>
/etc/66/stage3
</em></tt>
will be called.
Also, 66 tools
do not
provide
this
script
s
. It's the responsability
of the system administrator to
furnish
it.
<tt><em>
/etc/66/stage3
</em></tt>
will be called.
None of the 66 tools will
provide
such a
script. It's the responsability
of the system administrator to
provide
it.
</li>
<li>
<tt>
-e
<em>
environment
</em></tt>
: merge the current
environment variable of the scandir with variables found in the
environment variable
s
of the scandir with variables found in the
<em>
environment
</em>
directory. Any file in
<tt><em>
environment
</em></tt>
not beginning with a dot and not containing the '=' character will
be read. An absolute path is expected.
...
...
@@ -105,7 +105,7 @@
<li>
<tt>
-r
</tt>
: remove the scandir directory at
<em>
live
</em>
.
If it was already started with
<tt><em>
-u
</em></tt>
it must first
be stopped sending a signal with
<tt><em>
-s
</em></tt>
- see
"Signals" section
.
be stopped sending a signal with
e.g.
<tt><em>
‑
s quit
</em></tt>
- see
<a
href=
"#signals"
>
"Signals"
</a>
.
</li>
<li>
...
...
@@ -115,11 +115,11 @@
<li>
<tt>
-s
<em>
signal
</em></tt>
: send a
<em>
signal
</em>
to the scandir directory.
The signal can be any valid
<tt><a
href=
"https://skarnet.org/software/s6/s6-svscanctl.html"
>
s6
‑
svscanctl
</a></tt>
command or a predefined keyword - see
"Signals" section
.
command or a predefined keyword - see
<a
href=
"#signals"
>
"Signals
</a>
.
</li>
</ul>
<h2>
Signals
</h2>
<h2
id=
signals
>
Signals
</h2>
<p>
The
<em>
-s
</em>
option sends a signal to the scandir and is built
around the
<a
href=
"https://skarnet.org/software/s6/s6-svscanctl.html"
>
s6-svscanctl
</a>
.
...
...
@@ -131,13 +131,14 @@
A few convenient keywords were added to avoid having to remember
basic and useful series of commands like:
<ul>
<li><tt>
reload
</tt>
: this will send an
<em>
-an
</em>
command
</li>
<li><tt>
interrupt
</tt>
: this will send an
<em>
-i
</em>
command
</li>
<li><tt>
quit
</tt>
: this will send an
<em>
-q
</em>
command
</li>
<li><tt>
halt
</tt>
: this will send an
<em>
-0
</em>
command
</li>
<li><tt>
reboot
</tt>
: this will send an
<em>
-6
</em>
command
</li>
<li><tt>
poweroff
</tt>
: this will send an
<em>
-7
</em>
command
</li>
</ul></p>
<li><tt>
reload
</tt>
: equal to
<tt><strong><em>
‑
an
</em></strong></tt></li>
<li><tt>
interrupt
</tt>
: equal to
<tt><strong><em>
‑
i
</em></strong></tt></li>
<li><tt>
quit
</tt>
: equal to
<tt><strong><em>
‑
q
</em></strong></tt></li>
<li><tt>
halt
</tt>
: equal to
<tt><strong><em>
‑
0
</em></strong></tt></li>
<li><tt>
reboot
</tt>
: equal to
<tt><strong><em>
‑
6
</em></strong></tt></li>
<li><tt>
poweroff
</tt>
: equal to
<tt><strong><em>
‑
7
</em></strong></tt></li>
</ul>
</p>
<h3>
Signal usage examples
</h3>
<pre>
66
‑
scandir
‑
s reload
</pre>
...
...
@@ -208,7 +209,7 @@
the same
<tt><em>
owner
</em></tt>
you must delete it first with
<tt>
‑
r
</tt>
.
</p>
<h3>
.s6
‑
svscan control directory
</h3>
<h3
id=
"svscanctld"
>
.s6
‑
svscan control directory
</h3>
<p>
<tt><a
href=
"https://skarnet.org/software/s6/s6-svscan.html"
>
s6
‑
svscan
</a></tt>
...
...
@@ -390,7 +391,7 @@
<pre><tt>
/etc/66/env/TZ
</tt></pre>
<p>
Content of the file:
</p>
<pre><tt>
Pacific/Noumea
</tt></pre>
<p>
Every daemon launched on the scandir should inherit
s
the environment
<p>
Every daemon launched on the scandir should inherit the environment
variables of the scandir. So if you want to have a specific
<em>
key=value
</em>
pair for every daemon, use this option.
</p>
...
...
@@ -406,13 +407,13 @@
<ul>
<li>
<tt>
/run/66/scandir/0 will be
remov
ed
</tt>
<tt>
/run/66/scandir/0
#
will be
delet
ed
</tt>
</li>
<li>
<tt>
/run/66/tree/0 will be
remov
ed
</tt>
<tt>
/run/66/tree/0
#
will be
delet
ed
</tt>
</li>
<li>
<tt>
/run/66/log/0 will be
remov
ed
</tt>
<tt>
/run/66/log/0
#
will be
delet
ed
</tt>
</li>
</ul>
...
...
@@ -423,12 +424,13 @@
use it. In fact
<tt>
66
‑
scandir
</tt>
will only remove the
subdirectories of the corresponding UID of the
<tt><em>
owner
</em></tt>
and the
<tt><em>
live
</em></tt>
root directory is not touched.
As
<tt><em>
live
</em></tt>
should be created on RAM filesystem the deletion happen on next reboot.
As
<tt><em>
live
</em></tt>
should be created on a RAM filesystem
the deletion happens on the next reboot.
</p>
<p>
<strong>
Note
</strong>
: A running scandir can not be removed.
You must stop it with
<tt>
‑
d
</tt>
first to
You must stop it with
e.g.
<tt>
‑
s quit
</tt>
first to
be able to remove it.
</p>
</body>
...
...
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