Fossil

Check-in [bc678e13]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Clarity tweak
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | server-docs
Files: files | file ages | folders
SHA3-256: bc678e1321917b1d2a569c506147b216da8347b6d79a2823556b7a487c50ab53
User & Date: wyoung 2019-08-19 05:00:11
Context
2019-08-19
09:10
Added www/server/debian/service.md, demonstrating systemd configuration of Fossil for the first time in the official docs, both as a user serivce and in socket activation mode as a system-level service. check-in: 94763aed user: wyoung tags: server-docs
05:00
Clarity tweak check-in: bc678e13 user: wyoung tags: server-docs
04:58
Grammar fix on previous check-in: d5c754f9 user: wyoung tags: server-docs
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/server/windows/none.md.

25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
[si10]: https://www.tenforums.com/tutorials/2944-add-delete-enable-disable-startup-items-windows-10-a.html
[si7]:  https://www.wikihow.com/Change-Startup-Programs-in-Windows-7



## No Simple Background Mode

Windows also lacks a direct equivalent of the “`&`” control operator to
run a program in the background, which you can give in the `rc.local`
file, which is just a normal Bourne shell script.

I don’t mean “background” in the sense of “has no user interface,” I
mean in the sense “not attached to any user’s login session.” When the
`rc.local` script exits in Unix, any program it backgrounded *stays
running*. There is no simple and direct equivalent to this mechanism in
Windows.







|
|







25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
[si10]: https://www.tenforums.com/tutorials/2944-add-delete-enable-disable-startup-items-windows-10-a.html
[si7]:  https://www.wikihow.com/Change-Startup-Programs-in-Windows-7



## No Simple Background Mode

Windows also lacks a direct equivalent of the Bourne shell’s “`&`” control operator to
run a program in the background, which you can give in Unix’s `rc.local`
file, which is just a normal Bourne shell script.

I don’t mean “background” in the sense of “has no user interface,” I
mean in the sense “not attached to any user’s login session.” When the
`rc.local` script exits in Unix, any program it backgrounded *stays
running*. There is no simple and direct equivalent to this mechanism in
Windows.