Skip to content

Commit 27ecf5a

Browse files
committed
Improve enabling command expansion section (neo4j#2470)
1 parent f27fc46 commit 27ecf5a

File tree

1 file changed

+19
-2
lines changed

1 file changed

+19
-2
lines changed

modules/ROOT/pages/configuration/command-expansion.adoc

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,14 +41,31 @@ Scripts and their syntax differ between operating systems.
4141

4242
== Enabling
4343

44-
The Neo4j startup script and the `neo4j` service can expand and execute the external commands by using the argument `--expand-commands`.
44+
To enable command expansion, you must add the `--expand-commands` argument to the Neo4j startup script or _neo4j.service_ file.
45+
46+
=== Starting Neo4j with command expansion
47+
48+
To start Neo4j with command expansion enabled, you can use the following command:
4549

4650
[source, shell]
4751
----
4852
bin/neo4j start --expand-commands
4953
----
5054

51-
If the startup script does not receive the `--expand-commands` argument, commands in the configuration file are treated as invalid settings.
55+
=== Enabling command expansion in Neo4j as a service
56+
57+
If you are using Neo4j as a service, you can enable command expansion by adding the `--expand-commands` argument to the _/etc/systemd/system/neo4j.service_  file.
58+
Otherwise, the commands in the configuration file are treated as invalid settings.
59+
60+
You must also add `Type=forking` under the `[Service]` section of _/etc/systemd/system/neo4j.service_ to allow for the command expansion.
61+
62+
[source]
63+
----
64+
[Service]
65+
Type=forking
66+
----
67+
68+
=== Security checks
5269

5370
Neo4j performs the following basic security checks on the _neo4j.conf_ file.
5471
If they fail, Neo4j does not evaluate the script commands in _neo4j.conf_, and the Neo4j process does not start.

0 commit comments

Comments
 (0)