On Friday, November 22, 2013 7:25:29 AM UTC-6, Martin Langhoff wrote: > > On Fri, Nov 22, 2013 at 5:34 AM, Felix Frank > <[email protected] <javascript:>> wrote: > > That's cool, I think we should be allowed to be grumpuses (grumpi?) here > :-) > >
But not wumpuses. All wumpuses must be hunted down. :-) > :-) > > > The whole cron.d thing is > > https://projects.puppetlabs.com/issues/746<https://www.google.com/url?q=https%3A%2F%2Fprojects.puppetlabs.com%2Fissues%2F746&sa=D&sntz=1&usg=AFQjCNHYnPjxEpjYeUBlkXTmCM5W7PBz-w>and > > > > I have started working on that, but it's far from becoming useful. > > > > We won't be able to deprecate the crontab provider any time soon, I > believe. > > Why not focus on a cron.d provider that is really solid, and then > start the crontab provider deprecation process (mediated by whatever > timeframe is appropriate)? > > Do all relevant cron implementations support cron.d? Solaris? BSD / OSX? All Linux distros that matter? Etc? I don't know, but I am doubtful. Moreover, it would be highly desirable to enable Puppet effectively to manage cron jobs that it did not create itself. The work that Felix has been doing goes in that direction (hurrah!). To the extent that that is a target, however, crontab support will be required as long as cron implementations support crontabs, and I don't foresee that going away any time soon, if ever. > > Personally, I think we should allow users to shoot themselves in their > > respective feet to their hearts content, if some of them think the > > facility for doing so can be worthwhile. > > Well, that is valid... only if the worth of the dangerous feature is > solid. IOWs, assume a few users will misunderstand or just plain not > read the docs and set it without meaning to. > > I guess I cannot see the value of purging entries _that puppet did not > install in the first place_. I mean, there are lots of odd jobs that I > get puppet to perform by getting it to execute a bit of shell code, > and "nuke all crontab data for this user" seems to fit :-) > > I don't understand that. I mean, I know that one can work around Puppet's limitations as to what cron jobs it can and can't manage, but inasmuch as it is stipulated that Puppet's built-in cron support is not sufficient, I don't understand why it should not seen as valuable to enhance Puppet's cron support. Even if the only enhancement is support for global purge, that would provide something that you can only approximate with Exec, unless possibly you use a lot more than just "a bit" of shell code. That is, you cannot easily and reliably avoid your Exec removing cron jobs that are under management. Yes, Puppet might then recreate such jobs in the same run, but the result is not equivalent if any other resource listens for events from those Cron resources. John -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/3ded18a4-223b-41f5-9020-64976dcd3caa%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
