The real issue was that cron was not working. The root passwords on these systems were expired and this prevents cron from executing on a user with an expired password. Once I reset all the passwords my test in cron.hourly worked, and tmpwatch should do its job.Just one thing I was unaware of. What threw me off was that one of those hosts downloads a product from Toronto every week and was working, but it was using my userid not root.
On 03/11/2015 07:18 PM, Richard Pieri wrote: > On 3/11/2015 3:18 PM, John Abreau wrote: >> Argument list too long? Tri find(1): > > I'd originally considered suggesting that you tweak the tmpwatch daily > crontab entry to be more aggressive since the default EL prune time is > 30 days but a separate pulse pruner crontab would be less disruptive. > > Personally, I don't find /tmp cleaners to be workarounds. They're part > of every normally functioning UNIX and Unix-alike that I've ever > managed even when I've had to roll my own. > _______________________________________________ Discuss mailing list [email protected] http://lists.blu.org/mailman/listinfo/discuss
