All, I'm surprised I haven't seen this here since I can't be the only one experiencing this. We have a class that uses the file type to create a mount point, an exec to create a file system, and then uses the mount type to mount it up. The problem is, with most Unix file systems, the permissions change on a mount point after the file system is mounted up. I can't call my file type which sets the permissions on the mount point again because it creates an execution loop. I can't create another resource which sets the permissions because I get a previously defined error. The only solution using Puppet natives so far is to run Puppet twice - which is unacceptable in most situations.
My fall back is to use another exec call to do exactly what the file definition of the mount point already does, but that goes against the philosophy of having Puppet aware of the state of the system. Anyone else already solved this? Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
