On Thursday, March 15, 2018 at 7:03:09 PM UTC, R.I. Pienaar wrote:
>
> When you don’t tell it you can’t have any expectations
>
My expectations was that it work in a UN*X fashion:
- s n i p --
turbo@host:~$ ls -l file
ls: cannot access 'file': No such file or directory
turbo@host:~$ sudo
> On 15 Mar 2018, at 18:55, Turbo Fredriksson wrote:
>
> Puppet version: 3.8 (old, but can't upgrade).
>
>
> I had a "file {}" resource "blow up" on me today, a crontab file that cron
> refused to load because
>
> (*system*file) WRONG FILE OWNER (/etc/cron.d/file)
>
> This because I di
Puppet version: 3.8 (old, but can't upgrade).
I had a "file {}" resource "blow up" on me today, a crontab file that cron
refused to load because
(*system*file) WRONG FILE OWNER (/etc/cron.d/file)
This because I didn't have any 'owner' or 'group' parameters to the "file
{}" resource.. I ha
