> On Feb 20, 2024, at 2:31 AM, Thomas Schmidt <tschm...@htwg-konstanz.de> wrote:
>
> OP did indeed mean `sysupgrade`,
which makes little sense _unless_ on -current, which will guarantee to break
this every sixth months when -current shifts about.
> but fwiw, `syspatch && reboot` reboots
> your system if a patch as applied. I got it in all of my servers'
> cronjobs.
Most of the patches don’t require a reboot. This idea sounds horrible for
uptime. Sorry. I’m not rebooting something because a font was patched…
>
> - Thomas
>
> Am 17.02.2024 um 02:24 schrieb obs...@loopw.com:
>>> On Feb 15, 2024, at 10:12 AM, b...@fea.st wrote:
>>> am I the only one using automatic OS updates
>>> 0 3 * * * root sysupgrade
>> Maybe you meant “syspatch” there?
>> Syspatching via cron is questionable - Some of the patches wont be loaded
>> until the box is rebooted.
>> I think its better to run either syspatch or sysupgrade when i’m in front of
>> the console and can deal with consequences.
