doc: update garlicd usage from the nix-shell
This commit is contained in:
parent
0e0bf9e7a7
commit
5fd2a62684
@ -394,10 +394,15 @@ Configure the garlic daemon (experimental)
|
|||||||
The garlic benchmark has a experimental daemon which can be used to
|
The garlic benchmark has a experimental daemon which can be used to
|
||||||
automatically launch the experiments in the
|
automatically launch the experiments in the
|
||||||
.I target
|
.I target
|
||||||
machine. In order to configure it, a folder must be accesible in the
|
machine. The daemon creates to FIFO pipes to communicate with the
|
||||||
build process. To enable it, add the following configuration line in the
|
experiment in the build environment:
|
||||||
|
.I run
|
||||||
|
and
|
||||||
|
.I completed .
|
||||||
|
In order to use it, an existing directory must be specified, where those
|
||||||
|
two files can be created. In the configuration file
|
||||||
.CI \(ti/.config/nix/nix.config
|
.CI \(ti/.config/nix/nix.config
|
||||||
file at xeon07:
|
in xeon07, append the following line:
|
||||||
.CS
|
.CS
|
||||||
extra-sandbox-paths = /garlic=\fI<bscpkgs dir>\fP/garlic/garlicd
|
extra-sandbox-paths = /garlic=\fI<bscpkgs dir>\fP/garlic/garlicd
|
||||||
.CE
|
.CE
|
||||||
@ -406,20 +411,17 @@ The
|
|||||||
component must be replaced to the
|
component must be replaced to the
|
||||||
.I full
|
.I full
|
||||||
path of the bscpkgs directory. Then, go to the
|
path of the bscpkgs directory. Then, go to the
|
||||||
.I garlic/garlid
|
.I garlic
|
||||||
directory and run the daemon:
|
directory and run
|
||||||
|
.CI nix-shell
|
||||||
|
to enter the shell. Finally, execute the daemon inside the nix shell:
|
||||||
.CS
|
.CS
|
||||||
\&./garlicd \fI<bscpkgs dir>\fP .
|
garlicd \fI<bscpkgs dir>\fP
|
||||||
.CE
|
.CE
|
||||||
Again, put the path to the bscpkgs directory as the first argument. The
|
Again, put the path to the bscpkgs directory as the first argument.
|
||||||
second directoty is where the daemon will create the two FIFO files:
|
Notice that the daemon stays running in the foreground, waiting for
|
||||||
.I run
|
submission jobs. At this moment, it can only process one experiment at a
|
||||||
and
|
time.
|
||||||
.I completed ,
|
|
||||||
to comunicate with the build process. Notice that the daemon stays
|
|
||||||
running in the foreground, waiting for submission jobs. At this moment,
|
|
||||||
it can only process one experiment at a time, and it it fails to run,
|
|
||||||
you should restart the daemon.
|
|
||||||
.\" ===================================================================
|
.\" ===================================================================
|
||||||
.NH 2
|
.NH 2
|
||||||
Configure the login and target (MareNostrum 4)
|
Configure the login and target (MareNostrum 4)
|
||||||
|
Loading…
Reference in New Issue
Block a user