Try this:
files:
(!cdev_null|cbind9_devs_null_repaired)
"${cbind_dir}/dev/null"
comment => "Fix null device permission",
perms => mog("666", "root", "root"),
create => "false";
(!cdev_random|cbind9_devs_random_repaired)
"${cbind_dir}/dev/random"
comment
Yes it is corrected on a subsequent activation, but that mean that between two
activation my configuration is false, and I don't want that.
I have fix my trouble with "-m 666" mknod option, so that the device are
created directly with the right permission, but my question is to understand
the no
My guess is that the files promises have already been "kept" on the first
pass, they are not corrected on second or third pass because they have already
been verified.
If you give us your verbose output it would help.
Is it not corrected on a subsequent activation? That would surprise me.
Forum: CFEngine Help
Subject: Normal ordering, files and commands
Author: stchesmeli
Link to topic: https://cfengine.com/forum/read.php?3,27135,27135#msg-27135
Hi all :)
I'm writing a bundle to manage chrooted bind9 configuration.
I need to create null and random device inside the chroot, with 66
