GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
@@ -12,7 +12,7 @@ By: Assistants of IF3230 - Parallel and Distributed Systems
** Environment Set **
-Set the following lines to ```/etc/profile```:
Set the following lines to ```/etc/profile```:
export PATH=$PATH:/usr/local/go/bin
...
...
@@ -38,7 +38,3 @@ By: Assistants of IF3230 - Parallel and Distributed Systems
## How to Run
- In release environment, please use ```nohup go run main.go & > my.log 2>&1&``` for running tracker process in background. After that, use ```echo $! > save_pid.txt``` to get Process ID.
## Additional Information
- Developer note: On release (32.46), use account 'freedomofkeima' for MySQL username and '167.205.32.46' for IP address.