Custom Query (894 matches)
Results (70 - 72 of 894)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #584 | desai | Jim Rowan <[email protected]…> | fixed | perms on /etc/bcfg2.conf on server conflict with new reporting system |
| Description |
If you run the web server as someone other than root, it needs to be able to read /etc/bcfg2.conf. 600 is too tight. bcfg2-admin init seems to set that. |
|||
| #687 | desai | solj | worksforme | paranoid not working |
| Description |
paranoid=true in info.xml does not give any backup file |
|||
| #359 | desai | [email protected]… | fixed | paranoid mode should be truly paranoid |
| Description |
Currently, in paranoid mode, bcfg2 will overwrite all config files without creating a backup if the directory /var/spool/bcfg2 doesn't exist. It probably shouldn't. If the admin went out of the way to specify "paranoid: true" and "bcfg2 -P", then they really want to have a record of any changes in config files. Quietly failing is not a very good behaviour. |
|||
Note: See TracQuery
for help on using queries.
