| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
doc/appendix/files/mysql.txt
doc/getting_started/index.txt
doc/server/plugins/structures/bundler/kernel.txt
src/lib/Bcfg2/Server/MultiprocessingCore.py
src/lib/Bcfg2/Server/Plugin/interfaces.py
src/lib/Bcfg2/Server/Plugins/Packages/Yum.py
src/lib/Bcfg2/Server/Plugins/Probes.py
src/lib/Bcfg2/Server/Plugins/SSHbase.py
|
| | |
|
| | |
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
src/lib/Bcfg2/settings.py
src/sbin/bcfg2-crypt
|
| |
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The various init scripts have the usual start, stop, and status
functions which are called from a case statement. The functions
even nicely return various values for success and failure.
Unfortunately, those values were not passed all the way back to the
calling shell.
Previously, the init scripts would return 0 if any of start, stop, or
status failed. This commit ensures that they they pass the return
value back to the caller.
Why does this matter? Well, beyond just being generally good
citizens, bcfg2's own chkconfig client tool expects stopped services
to return a non-zero exit code when their status function is called.
Otherwise it flags the service state as incorrect and tries to stop
it on every run.
|
| |
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
debian/bcfg2-server.install
doc/server/plugins/grouping/metadata.txt
src/lib/Bcfg2/Client/Client.py
src/lib/Bcfg2/Client/Tools/Portage.py
src/lib/Bcfg2/Client/Tools/RcUpdate.py
src/lib/Bcfg2/Client/Tools/YUM24.py
src/lib/Bcfg2/Client/Tools/__init__.py
src/lib/Bcfg2/Client/Tools/launchd.py
src/lib/Bcfg2/Options.py
src/lib/Bcfg2/Server/Core.py
src/lib/Bcfg2/Server/Plugin/helpers.py
src/lib/Bcfg2/Server/Plugins/Metadata.py
src/lib/Bcfg2/Server/models.py
src/lib/Bcfg2/Utils.py
src/sbin/bcfg2-info
src/sbin/bcfg2-test
testsuite/Testsrc/Testlib/TestClient/TestTools/Test_init.py
testsuite/Testsrc/test_code_checks.py
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
doc/appendix/contributors.txt
schemas/bundle.xsd
src/lib/Bcfg2/Client/Tools/__init__.py
src/lib/Bcfg2/Server/Encryption.py
src/lib/Bcfg2/Server/Lint/Genshi.py
src/lib/Bcfg2/Server/Plugins/Bundler.py
src/lib/Bcfg2/Server/Plugins/Decisions.py
src/lib/Bcfg2/Server/Plugins/TemplateHelper.py
src/sbin/bcfg2-test
testsuite/Testsrc/Testlib/TestClient/TestTools/TestPOSIX/Test__init.py
testsuite/Testsrc/Testlib/TestClient/TestTools/TestPOSIXUsers.py
testsuite/Testsrc/Testlib/TestServer/TestPlugin/Testhelpers.py
testsuite/Testsrc/Testlib/TestServer/TestPlugins/TestProperties.py
tools/bcfg2-profile-templates.py
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The various init scripts have the usual start, stop, and status
functions which are called from a case statement. The functions
even nicely return various values for success and failure.
Unfortunately, those values were not passed all the way back to the
calling shell.
Previously, the init scripts would return 0 if any of start, stop, or
status failed. This commit ensures that they they pass the return
value back to the caller.
Why does this matter? Well, beyond just being generally good
citizens, bcfg2's own chkconfig client tool expects stopped services
to return a non-zero exit code when their status function is called.
Otherwise it flags the service state as incorrect and tries to stop
it on every run.
|
| |_|/
|/| |
| | |
| | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |/
|/|
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | |
|
| | |
|
|/
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
| |
Due to the way that the server drops privs, the PID file has to be
saved into a subdirectory of /run.
|
|
|
|
|
|
|
|
|
|
|
| |
* Run the daemon with -D /run/bcfg2-server.pid. If you don't run it
with -D PID, it doesn't fork, and since the unit file is
Type=forking, the service eventually times out and fails.
* Use the PIDFile unit option to give systemd a hint where the PID
file is located. This is recommended when using Type=forking by the
systemd documentation.
* Use $BCFG2_SERVER_OPTIONS, which is defined in
/etc/sysconfig/bcfg2-server, instead of $OPTIONS, which is not.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
| |
This reverts commit a20c012fca62bec92f3e99369ed6581485e8a153.
|
| |
|
| |
|
|
|
|
| |
dropping
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Change init scripts for both client and server:
- Don't run in runlevel 2; autofs and others are disabled there
- Start service much later, closer to httpd, after autofs has started
- Stop service much sooner, near same services as start
(cherry picked from commit c8e464d6cf0a5e099a9e6d41e943447db26ed8b9)
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixing this script for RedHat; its advantage over the Debian script
is the dependency on lsb drags in quite a number of extra, otherwise-
unneeded packages.
- Remove agent functions from bcfg2.init
- Add success || failure messages
- Include options from /etc/sysconfig/bcfg2*
- Other snippets from debian script
(cherry picked from commit 4034d6e503f1543223355f7aceb6aefd933fabb3)
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
Conflicts:
misc/bcfg2.spec
setup.py
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added bcfg2-yum-helper to offload Yum API calls to a short-lived
process. As absurd as this is, it appears to be the standard way to
get around Yum's atrocious memory handling (cf. yum-updatesd).
* Added SourceInitError for non-fatal errors instantiating new
sources.
* Fixed bug that caused all cached data to be removed on server
startup (reported by mikemccllstr on IRC).
* Fixed a number of overly aggressive caching issues.
* Fixed the way sources are loaded at server startup.
* Fixed handling of Yum package groups.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|