You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/cluster/installation.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ client:
26
26
27
27
You can also set a time that the script should wait after a job has finished execution to give the system time to cool down. Please use the [calibrate script]({{< relref "/docs/installation/calibration" >}}) to fine tune this value.
28
28
29
-
After running a job the client program executes the `tools/cluster/cleanup.sh` script that does general house keeping on the machine. This is done in a batch fashion to not run when a benchmark is currently run.
29
+
After running a job the client program executes the `tools/cluster/cleanup.py` script that does general house keeping on the machine. This is done in a batch fashion to not run when a benchmark is currently run.
30
30
31
31
To make sure that the client is always running you can create a service that will start at boot and keep running.
32
32
@@ -63,12 +63,12 @@ systemctl --user status green-coding-client # check status
63
63
64
64
You should now see the client reporting it's status on the server. It is important to note that only the client ever talks to the server (polling). The server never tries to contact the client. This is to not create any interrupts while a measurement might be running.
65
65
66
-
After running a job the client program executes the `tools/cluster/cleanup.sh` script that does general house keeping on the machine. This is done in a batch fashion to not run when a benchmark is currently run.
66
+
After running a job the client program executes the `tools/cluster/cleanup.py` script that does general house keeping on the machine. This is done in a batch fashion to not run when a benchmark is currently run.
67
67
68
68
This script is run as root and thus needs to be in the `/etc/sudoers` file or subdirectories somewhere. We recommend the following:
69
69
70
70
```bash
71
-
echo 'ALL ALL=(ALL) NOPASSWD:/home/gc/green-metrics-tool/tools/cluster/cleanup.sh ""' | sudo tee /etc/sudoers.d/green-coding-cluster-cleanup
71
+
echo 'ALL ALL=(ALL) NOPASSWD:/home/gc/green-metrics-tool/tools/cluster/cleanup.py ""' | sudo tee /etc/sudoers.d/green-coding-cluster-cleanup
0 commit comments