So I would use puppet to create the symlink or in your cause looks like you are doing this via RPM??
Then I would use puppet to create a cron to check if the symlink is still valid and if not create it, set this to run after your scheduled maintenance time. On Fri, Dec 30, 2011 at 11:32 AM, Len Rugen <lenru...@gmail.com> wrote: > We have a case where we've been requested to create an extra symlink. The > system provides libsomething.so.0.vv.rr and a symlink of > libsomething.so.0. We need create a symlink libsomething.so (without the > .0). I'm afraid maintenance may change the base file and break the > puppeted symlink. > > Can we do something like subscribe to the RPM provided libsomething.so.0 > link, then fire an script to find it's new target and recreate our > symlink? > > Thanks > > -- > 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. > -- *- Shawn Taaj* -- 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.
