Re: [Puppet Users] puppet cron jobs overwhelming host

2015-05-04 Thread Neil
Hello Looks like your intent is to run that daily? I'd use cron.daily for that. That mean you script runs even if the server is not on at midnight. what web applications do you run? You do NOT generally want apache owning the web content. Apache should mostly have read access and only write to f

Re: [Puppet Users] puppet cron jobs overwhelming host

2015-05-01 Thread Tim Dunphy
> Also you could consider wrapping these in a flock to prevent actions piling= > up behind each other - like described here: > http://www.elevatedcode.com/2013/05/07/flock-for-cron-jobs.html > > Many other examples on the net. Ok, Dan. That's really good info! Thanks and I'll be sure to check it

Re: [Puppet Users] puppet cron jobs overwhelming host

2015-05-01 Thread Denmat
Also you could consider wrapping these in a flock to prevent actions piling up behind each other - like described here: http://www.elevatedcode.com/2013/05/07/flock-for-cron-jobs.html Many other examples on the net. Den On 2 May 2015, at 04:15, Tim Dunphy wrote: >> In addition to Peter's exce

Re: [Puppet Users] puppet cron jobs overwhelming host

2015-05-01 Thread Tim Dunphy
> > In addition to Peter's excellent catch of the scheduling issue, depending > on how many files you have in /var/www and how much other contention there > is for disk I/O, your find commands could simply be getting bogged down > traversing the directory tree. They are pretty inefficient, as writt

Re: [Puppet Users] puppet cron jobs overwhelming host

2015-05-01 Thread Peter Bukowinski
> On May 1, 2015, at 12:52 PM, Tim Dunphy wrote: > > This isn't really a Puppet problem, but regardless: > Those cron entries are for "every minute during the zeroth hour". So at 00:00 > it will run, then at 00:01, then 00:02, and so > on all the way to 00:59, then will stop until 00:00 the nex

Re: [Puppet Users] puppet cron jobs overwhelming host

2015-05-01 Thread Tim Dunphy
> > This isn't really a Puppet problem, but regardless: > Those cron entries are for "every minute during the zeroth hour". So at > 00:00 it will run, then at 00:01, then 00:02, and so > on all the way to 00:59, then will stop until 00:00 the next day. Therefore, > if the chmod/chown processes tak

Re: [Puppet Users] puppet cron jobs overwhelming host

2015-05-01 Thread Peter Kristolaitis
On 05/01/2015 12:31 PM, Tim Dunphy wrote: That produces the following crons in my crontab: # Puppet Name: chmod-files * 0 * * * /bin/find /var/www -type f -exec chmod -v 664 {} \; # Puppet Name: apache-chown * 0 * * * /bin/chown -R apache:ftpgroup /var/www # Puppet Name: chmod-directories * 0

[Puppet Users] puppet cron jobs overwhelming host

2015-05-01 Thread Tim Dunphy
Hey guys, Ok, so I've run into a situation where I setup some cron jobs via puppet that do chown's and chmod's to make sure the web directory is owned by the web server and that the contents have the right permissions. The idea was to have the developer push their code via subversion and then ha