blob: e4030783d3c3d6f6c8ebfc43dd76ac6cb9b6b0d7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
post_install() {
# Note admin after install/update on how to change th update_check setting.
cat << _EOF
==> Globus Connect Personal install note:
------------------------------------------------------------------------------
You must create an endpoint before using Globus Connect Personal.
To set up the endpoint, follow the instruction at
https://docs.globus.org/how-to/globus-connect-personal-linux/#globus-connect-personal-cli
to generate a setup key, and run the command below:
globusconnect -setup <your-setup-key>
To autostart Globus Connect Personal service, you have two options: a system service or a
user service.
Running as a system service ensures that GCP service is run at startup even if the user has
no active session. Since the system service keeps GCP running even without an active user
session, it is intended to be used on a server.
To enable and start the system service:
# systemctl enable globus-connect-personal@myuser.service
# systemctl start globus-connect-personal@myuser.service
where myuser is the actual name of your user.
Running as a user service ensures that GCP only starts after the user has logged into the
system (e.g. via the graphical login screen, or ssh). Thus, the user service is intended to
be used on a (multiuser) desktop computer. It avoids unnecessarily running GCP instances.
To enable and start the user service:
$ systemctl --user enable globus-connect-personal.service
$ systemctl --user start globus-connect-personal.service
By default Globus Connect Personal will share your HOME folder. To configure which
directories are accessible to Globus Connect Personal, follow the instructions at
https://docs.globus.org/faq/globus-connect-endpoints/#how_do_i_configure_accessible_directories_on_globus_connect_personal_for_linux
_EOF
}
post_upgrade() {
post_install $1
}
post_remove() {
:
}
|