ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/gvpe/doc/gvpe.5.pod
(Generate patch)

Comparing gvpe/doc/gvpe.5.pod (file contents):
Revision 1.12 by root, Wed Nov 2 06:54:13 2016 UTC vs.
Revision 1.13 by root, Wed Nov 2 06:58:35 2016 UTC

… …
250 250
251=head2 STEP 5: enjoy 251=head2 STEP 5: enjoy
252 252
253... and play around. Sending a -HUP (C<gvpectrl -kHUP>) to the daemon 253... and play around. Sending a -HUP (C<gvpectrl -kHUP>) to the daemon
254will make it try to connect to all other nodes again. If you run it from 254will make it try to connect to all other nodes again. If you run it from
255inittab, as is recommended, C<gvpectrl -k> (or simply C<killall gvpe>) will 255inittab C<gvpectrl -k> (or simply C<killall gvpe>) will kill the daemon,
256kill the daemon, start it again, making it read it's configuration files 256start it again, making it read it's configuration files again.
257again.
258 257
259To run the GVPE daemon permanently, you can either add it to your SysV 258To run the GVPE daemon permanently from your SysV init, you can add it to
260F<inittab>, e.g.: 259your F<inittab>, e.g.:
261 260
262 t1:2345:respawn:/bin/sh -c "exec nice -n-20 /path/to/gvpe -D node >/var/log/gvpe.log 2>&1" 261 t1:2345:respawn:/bin/sh -c "exec nice -n-20 /path/to/gvpe -D node >/var/log/gvpe.log 2>&1"
263 262
264For systems using systemd, you can use a unit file ike this one: 263For systems using systemd, you can use a unit file similar to this one:
265 264
266 [Unit] 265 [Unit]
267 Description=gvpe 266 Description=gvpe
268 After=network.target 267 After=network.target
269 Before=remote-fs.target 268 Before=remote-fs.target

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines