Jarrod Johnson 9b48110155 Do not proceed a logged, but broken session ...

It shouldn't be possible for this to be the case, but out of an
abundance of caution, check for this.  So far only produced this by
forcing broken = True in a debug session.  Intended to catch an alleged
scenario where console was managing to use a broken session (fixed in
pyghmi) and have confluent also recognize the situation for non-console
usage).

2018-08-16 14:43:16 -04:00

..

bin

Have collective show present some info when not in quorum

2018-07-20 14:11:38 -04:00

confluent

Do not proceed a logged, but broken session

2018-08-16 14:43:16 -04:00

dbgtools

Fix confluentdbgcli on screen resize

2018-03-01 13:39:25 -05:00

sysctl

Tune the UDP receive buffer

2017-08-11 15:43:44 -04:00

systemd

Correct some minor potential issues and add restart on failure

2017-08-25 16:41:22 -04:00

sysvinit

…

buildrpm

Implement Lenovo Thinksystem and discovery support

2017-06-20 14:56:24 -04:00

confluent_server.spec.tmpl

Relax cryptodomex requirement

2018-07-10 10:10:04 -04:00

confluentdbgcli.py

Provide a script to summarize hangtraces files

2017-05-22 09:25:51 -04:00

confluentsrv.spec

…

makesetup

Fix makesetup for confluent_client

2018-04-10 16:11:14 -04:00

MANIFEST.in

Fix sysctl packaging info

2017-08-11 16:11:05 -04:00

requirements.txt

…

setup.cfg

…

setup.py.tmpl

Rename confluentutil to collective

2018-07-09 13:33:56 -04:00