On Wed, Jul 27, 2016 at 5:42 PM, Ruben Kerkhof wrote:
> On Wed, Jul 27, 2016 at 5:17 PM, John Florian wrote:
>> How can this metadata be leveraged with automation? I have the dnf
>> tracer plugin which I believe is using this metadata to tell me when I
>> need to reboot, but what if I have this
lag if
>>> you are using that to apply your updates. If you simply want to
>>> always be running the latest, then 'dnf update && reboot' solves that
>>> need.
>>
>> In the case I've been thinking of the updates are done by us, or
>> pup
ally boot into it.
>> I quite frequently skip non-security kernel updates if nothing else is
>> actually wrong. We fix bugs in a large number of places, and not all
>> of those places are things your machine might care about.
>
> My understanding of /var/run/reboot-re
#x27; or
> 'reboot-required'. There are many cases where a kernel update is
> pushed out but you might not have any reason to actually boot into it.
> I quite frequently skip non-security kernel updates if nothing else is
> actually wrong. We fix bugs in a large number of
On Wed, Jul 27, 2016 at 11:39 AM, Ruben Kerkhof wrote:
> On Wed, Jul 27, 2016 at 2:16 PM, Josh Boyer wrote:
>> Why would you want this to be something packaged? We have 'reboot
>> recommended' in our bodhi update metadata, and that seems like a much
>> better place for it.
>
> My guess is that '
On Wed, Jul 27, 2016 at 5:17 PM, John Florian wrote:
> How can this metadata be leveraged with automation? I have the dnf
> tracer plugin which I believe is using this metadata to tell me when I
> need to reboot, but what if I have this in a cron job?
The docs at http://dnf-plugins-extras.readth
On Wed, Jul 27, 2016 at 2:16 PM, Josh Boyer wrote:
> Why would you want this to be something packaged? We have 'reboot
> recommended' in our bodhi update metadata, and that seems like a much
> better place for it.
My guess is that 'reboot recommended' is true for each kernel update.
What I'd lik
t; >
> > One difference though is that unattended-upgrade drops a script in
> > /etc/kernel/postinst.d/unattended-upgrades, which does this:
> >
> > #!/bin/sh
> > if [ -d /var/run ]; then
> > touch /var/run/reboot-required
> > fi
> >
> > Using An
d/unattended-upgrades, which does this:
>
> #!/bin/sh
> if [ -d /var/run ]; then
> touch /var/run/reboot-required
> fi
>
> Using Ansible, I can quickly see which servers need a reboot due to a
> kernel upgrade.
>
> I think this would be nice to have in Fedora as well, th
/run/reboot-required
fi
Using Ansible, I can quickly see which servers need a reboot due to a
kernel upgrade.
I think this would be nice to have in Fedora as well, the only
question is which package
should provide it.
We have /etc/kernel/postinst.d too, but this directory is currently unowned.
So if
10 matches
Mail list logo
