| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | redhat/systemd: The bcfg2 client is not forking | Sol Jerome | 2013-12-24 | 1 | -1/+2 |
| | | | | | Signed-off-by: Sol Jerome <sol.jerome@gmail.com> | ||||
| * | redhat: Fix systemd script to use BCFG2_OPTIONS | Sol Jerome | 2013-12-07 | 1 | -1/+1 |
| | | | | | Signed-off-by: Sol Jerome <sol.jerome@gmail.com> | ||||
| * | Systemd: Fix path to PID file | Jonathan Billings | 2013-01-15 | 1 | -2/+2 |
| | | | | | | Due to the way that the server drops privs, the PID file has to be saved into a subdirectory of /run. | ||||
| * | Systemd: Fix server systemd unit | Jonathan Billings | 2013-01-15 | 1 | -1/+2 |
| | | | | | | | | | | | | * 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. | ||||
| * | changed default pidfile location in init scripts to allow easier privilege ↵ | Chris St. Pierre | 2012-10-04 | 1 | -1/+1 |
| | | | | | dropping | ||||
| * | Path fixed | Fabian Affolter | 2012-05-01 | 2 | -2/+2 |
| | | |||||
| * | Initial .service files added | Fabian Affolter | 2011-07-03 | 2 | -0/+26 |
 |
server / bcfg2 | |
| Custom fork of bcfg2 (configuration management) | spline |
| summaryrefslogtreecommitdiffstats |