Custom Query (894 matches)
Results (4 - 6 of 894)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#997 | desai | Arto Jantunen <[email protected]…> | fixed | bcfg2-ping-sweep has no documentation |
Description |
The bcfg2-ping-sweep command appears to lack documentation, it does not have a man page or even a --help command line option. This issue was filed in the Debian BTS as bug #608611, see http://bugs.debian.org/608611 |
|||
#998 | desai | Arto Jantunen <[email protected]…> | invalid | Reloading services on Debian systems |
Description |
Currently on a Debian system the bcfg2 client reloads a service by calling /etc/init.d/<service> restart, when in many cases a reload would be enough. The Debian Policy does not define the reload action, so it may or may not exist, depending on package. However the Policy does guarantee the existance of the force-reload action. In packages that can reload themselves without restarting force-reload does a reload, and in packages that cannot it does a restart. In my understanding that makes force-reload the correct action for bcfg2 to take for reloading services on Debian systems. I would submit a patch for this, but I'm not entirely sure what is the correct way to implement it. Simply always replacing restart with force-reload in src/lib/Client/Tools/DebInit.py may not be the correct solution since in some cases a real restart may be required and doing that would prevent forcing restarts where needed. This issue was filed as bug #406288 in the Debian BTS, see http://bugs.debian.org/406288 |
|||
#421 | desai | [email protected]… | fixed | "Preserving" timestamps of config files |
Description |
It would be nice to be able to control the mtime of configuration files. This could be done in two ways:
The former looks like the nicer way for people copying over config files as bases into the Cfg subdir. But the latter method fits better with bcfg2's general philosophy. It also looks much easier to implement. Thanks! |