Once upon a time, Tony Mountifield said:
> That shouldn't matter. The running programs will have mapped the original
> glibc into memory, which will create a reference to the original inode, even
> though the directory entries pointing to it are gone. See the output of "lsof"
> for one of those
On Sat, Apr 13, 2019 at 01:32:11AM -0700, Kenneth Porter wrote:
> I reboot when I yum update to a new kernel or systemd, which seems to come
> out about once a month. Should I do it for this week's glibc? Is that "core"
> enough to justify a reboot or should I wait for the next kernel update? I
>
On Apr 13, 2019, at 2:32 AM, Kenneth Porter wrote:
>
> I reboot when I yum update to a new kernel or systemd, which seems to come
> out about once a month.
You can use similar logic as in Tony Mountfield’s answer to put off reboots in
those cases as well.
If the reason for the kernel update
On 4/13/19 3:32 AM, Kenneth Porter wrote:
I reboot when I yum update to a new kernel or systemd, which seems to
come out about once a month. Should I do it for this week's glibc? Is
that "core" enough to justify a reboot or should I wait for the next
kernel update?
This is basically your
In article ,
Kenneth Porter wrote:
> I reboot when I yum update to a new kernel or systemd, which seems to come
> out about once a month. Should I do it for this week's glibc? Is that
> "core" enough to justify a reboot or should I wait for the next kernel
> update? I know the glibc update was
I reboot when I yum update to a new kernel or systemd, which seems to come
out about once a month. Should I do it for this week's glibc? Is that
"core" enough to justify a reboot or should I wait for the next kernel
update? I know the glibc update was mainly to handle the new Japanese
6 matches
Mail list logo
