Striker-manage-peers
Alteeve Wiki :: Man Pages :: Striker-manage-peers |
NAME
striker-manage-peers - This manages peering two Striker dashboards
SYNOPSIS
striker-manage-peers <command> [options]
DESCRIPTION
This handles peering Striker dashboards. Peered Strikers means that they act as replaceable alternative dashboards, should another fail.
OPTIONS
- -?, -h, --help
- Show this man page.
- --log-secure
- When logging, record sensitive data, like passwords.
- -v, -vv, -vvv
- Set the log level to 1, 2 or 3 respectively. Be aware that level 3 generates a significant amount of log data.
Commands:
- --check
- This reports 'status=[1,0]' to indicate if the install target feature is currently running or not. Specifically, it checks to see if the DHCP server is running or not.
- --disable
- This disables the install target feature.
- --enable
- This enables the install target feature.
- --force
- This is the same as '--refresh', forcing the update of the RPM repo.
- --job-uuid <uuid>
- This is the job UUID used to run this job.
- --no-refresh
- If a refresh of the RPM repository would have been called, this switch will prevent it from happening.
- --refresh-file
- This tells this run to refresh the RPM repository, regardless of whether it would have run otherwise.
- --status
- This checks to see if dhcpd is running or not, then exits (effectively checking if the install target feature is running).
AUTHOR
Written by Madison Kelly, Alteeve staff and the Anvil! project contributors.
REPORTING BUGS
Report bugs to users@clusterlabs.org
Any questions, feedback, advice, complaints or meanderings are welcome. | |||
Alteeve's Niche! | Alteeve Enterprise Support | Community Support | |
© 2025 Alteeve. Intelligent Availability® is a registered trademark of Alteeve's Niche! Inc. 1997-2025 | |||
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions. |