Running portupgrade from cron (was: /usr/bin/script eating 100% cpu
with portupgrade and xargs)
stb at lassitu.de
Sun Oct 23 10:32:55 UTC 2011
Am 23.10.2011 um 08:47 schrieb Chris Rees:
> Worst of all, you're running portupgrade from cron without reading UPDATING,
> which is just asking for trouble.
What specifically is your concern here?
I've been running portupgrade from cron for six years on a multitude of systems with great success. Yes, occasionally, things break, and reading UPDATING becomes a necessity, but I much prefer the nightly upgrade to running portupgrade by hand less frequently, especially when you have to do it on 20 or more machines.
Note that most of these boxes have very limited SLAs, and dealing with the occasional breakage is much less work than regular manual maintainance.
I decided to do this after I got bitten one too many times trying to upgrade ports after three to four months, and getting stuck in all kinds of bad dependencies. Daily upgrades usually means that I catch every single update by itself, so complex interdependencies are exactly what the committer tested.
Stefan Bethke <stb at lassitu.de> Fon +49 151 14070811
More information about the freebsd-stable