Modify

Ticket #763 (closed enhancement: fixed)

Opened 10 years ago

Last modified 10 years ago

RFE - bcfg2.conf option to assert paranoid mode

Reported by: ITS Systems Bcfg2 Team <systems-unix-cfg@…> Owned by: solj
Priority: minor Milestone: Bcfg2 1.0.0 Release
Component: bcfg2-client Version: 1.0
Keywords: paranoid config file Cc: solj@…

Description

We are currently running 1.0pre5 and are experimenting with paranoid mode.

Currently the only way to specify paranoid mode seems to be the use of the -P command line option. It would be helpful to also have a config file option available to specify paranoid behavior whenever the Bcfg2 client is run.

It is of course possible to change the command line options that the automated cron jobs run. However, in the name of consistency between interactive and automated use, it would be helpful to be able to uniformly assert a site-specific policy to be paranoid in the config file as well.

Attachments

Change History

comment:1 follow-up: ↓ 2 Changed 10 years ago by solj

  • Owner changed from desai to solj
  • Status changed from new to accepted

You should be able to set a global paranoid setting in bcfg2.conf with the following:

[mdata]
paranoid=true

comment:2 in reply to: ↑ 1 ; follow-up: ↓ 3 Changed 10 years ago by ITS Systems Bcfg2 Team <systems-unix-cfg@…>

Replying to solj:

You should be able to set a global paranoid setting in bcfg2.conf with the following:

[mdata]
paranoid=true

Thanks for your response. According to Changeset 5308, this would sets the default file metadata to "paranoid=true" for all files. It's great to know that it is possible to change the default metadata settings in this way.

However, setting these default metadata attributes does not seem to have the effect of actually triggering paranoid behavior. In a test just now, even with the [mdata] setting above, I still have to use the -P option to see any prior file contents stored in /var/cache/bcfg2 afterward.

comment:3 in reply to: ↑ 2 Changed 10 years ago by solj

  • Status changed from accepted to closed
  • Resolution set to fixed
  • Milestone set to Bcfg2 1.0.0 Release

Replying to ITS Systems Bcfg2 Team <systems-unix-cfg@…>:

Replying to solj:

You should be able to set a global paranoid setting in bcfg2.conf with the following:

[mdata]
paranoid=true

Thanks for your response. According to Changeset 5308, this would sets the default file metadata to "paranoid=true" for all files. It's great to know that it is possible to change the default metadata settings in this way.

However, setting these default metadata attributes does not seem to have the effect of actually triggering paranoid behavior. In a test just now, even with the [mdata] setting above, I still have to use the -P option to see any prior file contents stored in /var/cache/bcfg2 afterward.

Right, I realized this after responding to your ticket. You should be able to set this permanently in bcfg2.conf on the client like this:

[client]
paranoid = true

This is added in [3f4cfa355f9f3c20a1c9dd13bd224416995be100] (SVN r5482).

comment:4 Changed 10 years ago by solj

  • Cc solj@… added

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.