Rudder

Dennis, I'm not sure I really understand what's going on here. How did you attempt to modify this file? Which Technique (and version) did you use, was it a file copy, or a file edit? And what errors did you encounter? Some logs would be useful, also.

It's a file edit. In the same way I edited other files within the same directive. There are no useful errors, only "The file /etc/services could not be updated". Also in syslog on the rudder-client this is the only message that appears. "Force file contents" box is not ticked, because I just need to append some services.

I will send the promise file tomorrow. Thanks for your update.

Thanks for this Dennis. I just checked your file and it seemed to contain some sensitive data internal to your organization. As a precautionary measure, I have removed it from the bugtracker.

Could you check, and confirm that this info is public, or obfuscate it in the file, and resend?

Finally I found the problem in the CFengine logs:

!! File /etc/services is bigger than the limit edit.max_file_size = 362031 > 0 bytes
File /etc/services was marked for editing but could not be opened

And here is the fix:

--- /var/rudder/share/ce7836bf-d512-4282-9240-26ffec2c5b49/rules/cfengine-community/common/1.0/rudder_lib.cf.orig    2013-04-09 17:01:55.336441268 +0200
+++ /var/rudder/share/ce7836bf-d512-4282-9240-26ffec2c5b49/rules/cfengine-community/common/1.0/rudder_lib.cf    2013-04-09 17:08:37.307669649 +0200
@@ -139,14 +139,14 @@
 {
 empty_file_before_editing => "false";
 edit_backup => "timestamp";  # we want to keep a track of everything
-max_file_size => "300000";
+max_file_size => "1024000";
 }

 body edit_defaults empty_backup
 {
 empty_file_before_editing => "true";
 edit_backup => "timestamp";
-max_file_size => "300000";
+max_file_size => "1024000";
 }

@@ -337,7 +337,7 @@
 body edit_defaults rudder_empty_select(select)
 {
 empty_file_before_editing => "$(select)";
-max_file_size => "300000";
+max_file_size => "1024000";
 edit_backup => "timestamp";
 }

Oops, sorry I misunderstood what you are trying to do.

Well, OK this is a totally valid fix then, disregard what I said in #10.

Checked in all the PT/Techniques, there is no side effect when modifying max_file_size. Green light.

Applied in changeset policy-templates:commit:72bd1a59bf8ba9f6cc2b81d0c978d51b023f1d58.