On Oct 28, 9:33 am, Nigel Kersten <[email protected]> wrote: > On Thu, Oct 28, 2010 at 12:02 AM, donavan <[email protected]> wrote: > > Your objection to launchd provider start, stop, enable, & disable > > always writing as xml regardless of original format. I assume this is > > part of #4841? The binary -> xml behavior isnt as import as getting > > #5112 fixed, to me. > > Getting things working is more important than perfect behavior, yes :) > > I am opposed to us twiddling formats of property lists unless we > absolutely have to. It would mean we could easily get into situations > where Puppet repeatedly downloads a launchd plists because the format > has changed compared to the server version, which can easily lead to > unnecessary and intrusive service restarts. > > It also affects people running file-based tripwire style systems such > as radmind.
Sounds good to me. I'd +1 respecting the original plist format if possible. > > As I mentioned in #5112 it looks like Puppet::Error.new was raised, > > but the reports did not contain the error. Because of that all my > > catalogs were passing, though applying 0 resources. New issue or am I > > missing something obvious? > > I think that's a separate issue. I'll try to spend some time getting a test case then open a new issue for this. > > Markus got it right for me. I meant dash not slash. Looks like /- > > ( filename dash in root directory ) was created on my affected > > machines. Dunno if that's worth an errata against 2.6.2 or not. > > oh no. :( So this file was only created on 10.4 machines who ran 2.6.2 right? Yup. I have a few dozen 10.4 machines that had 2.6.2 installed. They all have the contents of the last parsed plist in the /- file. A spot check of 10.[5,6] machines doesn't show the same problem. I don't know how plausible it is but it could be information disclosure issue. The created files are all 644, so world readable. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
