Running portupgrade from cron (was: /usr/bin/script eating 100%
cpu with portupgrade and xargs)
basarevych at gmail.com
Sun Oct 23 11:35:28 UTC 2011
On Sun, Oct 23, 2011 at 2:14 PM, Stefan Bethke <stb at lassitu.de> wrote:
> Am 23.10.2011 um 13:11 schrieb Ross:
>> On Sun, Oct 23, 2011 at 1:32 PM, Stefan Bethke <stb at lassitu.de> wrote:
>>> 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?
>> And what you will get with ignoring /usr/ports/UPDATING when this happens:
>> AFFECTS: users of graphics/png
>> AUTHOR: dinoex at FreeBSD.org
>> The PNG library has been updated to version 1.4.1. Please rebuild all
>> ports that depend on it.
> And where exactly did I say that I never read UPDATING, and that I wouldn't follow it's instructions?
Yes, but updating correctly in first place is better than trying to
understand what happened to software looking for libpng.so.N when
there is libpng.so.N+1 and _then_ reading UPDATING is better, don't
Other point is that during update daemons never restarted. But
sometimes stopped, dovecot, for example, if I'm not mistaken. Do you
also reboot after each cron update?
> Stefan Bethke <stb at lassitu.de> Fon +49 151 14070811
More information about the freebsd-stable