yum packages update with excluding packages which need reboot [duplicate]

Multi tool use
Multi tool use

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite













This question already has an answer here:



  • Is there a way to permanently exclude the kernel from updates?

    1 answer



We are trying to update few yum packages but need to ensure that the packages which need to reboot are to be excluded.
Example : There are close to 500-1000 packages and I need to exclude kernel packages as we cannot update without security approval.
Is there any option in yum to handle this scenario?







share|improve this question














marked as duplicate by Jeff Schaller, Kusalananda, Isaac, h3rrmiller, Shadur Feb 10 at 9:26


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • The duplicate deals with the kernel; not generically “packages which need a reboot”
    – Jeff Schaller
    Feb 8 at 16:19










  • From vague memory: in the packages for autopatching (yum-cron?), there's a helper tool that "knows" if a reboot will be needed, the name of which I don't recall right now. That helper is a python script and contains a hardcoded list of packages that will require reboot. We can't know if that list is complete, but it seems good enough for RHEL.
    – Ulrich Schwarz
    Feb 8 at 16:54






  • 1




    @UlrichSchwarz you prompted me to come up with it: possibly needs-restarting, bubbling up from recent memory here
    – Jeff Schaller
    Feb 8 at 17:09











  • @JeffSchaller: That's the one, in yum-utils, quoting access.redhat.com/solutions/27943 (paywall) and listing 'kernel', 'glibc', 'linux-firmware', 'systemd', 'udev', 'openssl-libs', 'gnutls', 'dbus'. Bit surprised about gnutls and openssl-libs, I've got to say.
    – Ulrich Schwarz
    Feb 8 at 18:27










  • Just installing the updates won't force a reboot. You'll need to schedule one manually anyway, meaning you can get security approval when you do.
    – Shadur
    Feb 10 at 9:25














up vote
0
down vote

favorite













This question already has an answer here:



  • Is there a way to permanently exclude the kernel from updates?

    1 answer



We are trying to update few yum packages but need to ensure that the packages which need to reboot are to be excluded.
Example : There are close to 500-1000 packages and I need to exclude kernel packages as we cannot update without security approval.
Is there any option in yum to handle this scenario?







share|improve this question














marked as duplicate by Jeff Schaller, Kusalananda, Isaac, h3rrmiller, Shadur Feb 10 at 9:26


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • The duplicate deals with the kernel; not generically “packages which need a reboot”
    – Jeff Schaller
    Feb 8 at 16:19










  • From vague memory: in the packages for autopatching (yum-cron?), there's a helper tool that "knows" if a reboot will be needed, the name of which I don't recall right now. That helper is a python script and contains a hardcoded list of packages that will require reboot. We can't know if that list is complete, but it seems good enough for RHEL.
    – Ulrich Schwarz
    Feb 8 at 16:54






  • 1




    @UlrichSchwarz you prompted me to come up with it: possibly needs-restarting, bubbling up from recent memory here
    – Jeff Schaller
    Feb 8 at 17:09











  • @JeffSchaller: That's the one, in yum-utils, quoting access.redhat.com/solutions/27943 (paywall) and listing 'kernel', 'glibc', 'linux-firmware', 'systemd', 'udev', 'openssl-libs', 'gnutls', 'dbus'. Bit surprised about gnutls and openssl-libs, I've got to say.
    – Ulrich Schwarz
    Feb 8 at 18:27










  • Just installing the updates won't force a reboot. You'll need to schedule one manually anyway, meaning you can get security approval when you do.
    – Shadur
    Feb 10 at 9:25












up vote
0
down vote

favorite









up vote
0
down vote

favorite












This question already has an answer here:



  • Is there a way to permanently exclude the kernel from updates?

    1 answer



We are trying to update few yum packages but need to ensure that the packages which need to reboot are to be excluded.
Example : There are close to 500-1000 packages and I need to exclude kernel packages as we cannot update without security approval.
Is there any option in yum to handle this scenario?







share|improve this question















This question already has an answer here:



  • Is there a way to permanently exclude the kernel from updates?

    1 answer



We are trying to update few yum packages but need to ensure that the packages which need to reboot are to be excluded.
Example : There are close to 500-1000 packages and I need to exclude kernel packages as we cannot update without security approval.
Is there any option in yum to handle this scenario?





This question already has an answer here:



  • Is there a way to permanently exclude the kernel from updates?

    1 answer









share|improve this question













share|improve this question




share|improve this question








edited Feb 8 at 16:15









Jeff Schaller

31.3k846105




31.3k846105










asked Feb 8 at 16:11









user227863

144




144




marked as duplicate by Jeff Schaller, Kusalananda, Isaac, h3rrmiller, Shadur Feb 10 at 9:26


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






marked as duplicate by Jeff Schaller, Kusalananda, Isaac, h3rrmiller, Shadur Feb 10 at 9:26


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.













  • The duplicate deals with the kernel; not generically “packages which need a reboot”
    – Jeff Schaller
    Feb 8 at 16:19










  • From vague memory: in the packages for autopatching (yum-cron?), there's a helper tool that "knows" if a reboot will be needed, the name of which I don't recall right now. That helper is a python script and contains a hardcoded list of packages that will require reboot. We can't know if that list is complete, but it seems good enough for RHEL.
    – Ulrich Schwarz
    Feb 8 at 16:54






  • 1




    @UlrichSchwarz you prompted me to come up with it: possibly needs-restarting, bubbling up from recent memory here
    – Jeff Schaller
    Feb 8 at 17:09











  • @JeffSchaller: That's the one, in yum-utils, quoting access.redhat.com/solutions/27943 (paywall) and listing 'kernel', 'glibc', 'linux-firmware', 'systemd', 'udev', 'openssl-libs', 'gnutls', 'dbus'. Bit surprised about gnutls and openssl-libs, I've got to say.
    – Ulrich Schwarz
    Feb 8 at 18:27










  • Just installing the updates won't force a reboot. You'll need to schedule one manually anyway, meaning you can get security approval when you do.
    – Shadur
    Feb 10 at 9:25
















  • The duplicate deals with the kernel; not generically “packages which need a reboot”
    – Jeff Schaller
    Feb 8 at 16:19










  • From vague memory: in the packages for autopatching (yum-cron?), there's a helper tool that "knows" if a reboot will be needed, the name of which I don't recall right now. That helper is a python script and contains a hardcoded list of packages that will require reboot. We can't know if that list is complete, but it seems good enough for RHEL.
    – Ulrich Schwarz
    Feb 8 at 16:54






  • 1




    @UlrichSchwarz you prompted me to come up with it: possibly needs-restarting, bubbling up from recent memory here
    – Jeff Schaller
    Feb 8 at 17:09











  • @JeffSchaller: That's the one, in yum-utils, quoting access.redhat.com/solutions/27943 (paywall) and listing 'kernel', 'glibc', 'linux-firmware', 'systemd', 'udev', 'openssl-libs', 'gnutls', 'dbus'. Bit surprised about gnutls and openssl-libs, I've got to say.
    – Ulrich Schwarz
    Feb 8 at 18:27










  • Just installing the updates won't force a reboot. You'll need to schedule one manually anyway, meaning you can get security approval when you do.
    – Shadur
    Feb 10 at 9:25















The duplicate deals with the kernel; not generically “packages which need a reboot”
– Jeff Schaller
Feb 8 at 16:19




The duplicate deals with the kernel; not generically “packages which need a reboot”
– Jeff Schaller
Feb 8 at 16:19












From vague memory: in the packages for autopatching (yum-cron?), there's a helper tool that "knows" if a reboot will be needed, the name of which I don't recall right now. That helper is a python script and contains a hardcoded list of packages that will require reboot. We can't know if that list is complete, but it seems good enough for RHEL.
– Ulrich Schwarz
Feb 8 at 16:54




From vague memory: in the packages for autopatching (yum-cron?), there's a helper tool that "knows" if a reboot will be needed, the name of which I don't recall right now. That helper is a python script and contains a hardcoded list of packages that will require reboot. We can't know if that list is complete, but it seems good enough for RHEL.
– Ulrich Schwarz
Feb 8 at 16:54




1




1




@UlrichSchwarz you prompted me to come up with it: possibly needs-restarting, bubbling up from recent memory here
– Jeff Schaller
Feb 8 at 17:09





@UlrichSchwarz you prompted me to come up with it: possibly needs-restarting, bubbling up from recent memory here
– Jeff Schaller
Feb 8 at 17:09













@JeffSchaller: That's the one, in yum-utils, quoting access.redhat.com/solutions/27943 (paywall) and listing 'kernel', 'glibc', 'linux-firmware', 'systemd', 'udev', 'openssl-libs', 'gnutls', 'dbus'. Bit surprised about gnutls and openssl-libs, I've got to say.
– Ulrich Schwarz
Feb 8 at 18:27




@JeffSchaller: That's the one, in yum-utils, quoting access.redhat.com/solutions/27943 (paywall) and listing 'kernel', 'glibc', 'linux-firmware', 'systemd', 'udev', 'openssl-libs', 'gnutls', 'dbus'. Bit surprised about gnutls and openssl-libs, I've got to say.
– Ulrich Schwarz
Feb 8 at 18:27












Just installing the updates won't force a reboot. You'll need to schedule one manually anyway, meaning you can get security approval when you do.
– Shadur
Feb 10 at 9:25




Just installing the updates won't force a reboot. You'll need to schedule one manually anyway, meaning you can get security approval when you do.
– Shadur
Feb 10 at 9:25










2 Answers
2






active

oldest

votes

















up vote
1
down vote













RHEL and derivatives have needs-restarting in the yum-utils package, but that can only give you an after-the-fact evaluation. However, it is a python script, so we can peek inside to find the following hard-coded list of packages that will make it suggest a reboot:



# For which package updates we should recommend a reboot
# Taken from https://access.redhat.com/solutions/27943
REBOOTPKGS = ['kernel', 'glibc', 'linux-firmware', 'systemd', 'udev',
'openssl-libs', 'gnutls', 'dbus']


Note that this list might not be exhaustive. I'd need to double-check if RedHat recommends to their paying and supported customers to restart according to this heuristic when doing unattended updates, that would give me a bit more confidence.






share|improve this answer




















  • Quick check .. so post installing yum-utils .. need to run needs-restarting to check list of packages which require restart or reboot?
    – user227863
    Feb 8 at 19:25










  • Can we use show-installed | grep needs-restarting ?
    – user227863
    Feb 8 at 19:36

















up vote
0
down vote













Exclude a package from update : Edit /etc/yum.conf → add one or more "exclude" lines. https://tecadmin.net/exclude-packages-from-yum-update/



exclude=kernel*


Note : The wildcard ( * ) is important.






share|improve this answer



























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    1
    down vote













    RHEL and derivatives have needs-restarting in the yum-utils package, but that can only give you an after-the-fact evaluation. However, it is a python script, so we can peek inside to find the following hard-coded list of packages that will make it suggest a reboot:



    # For which package updates we should recommend a reboot
    # Taken from https://access.redhat.com/solutions/27943
    REBOOTPKGS = ['kernel', 'glibc', 'linux-firmware', 'systemd', 'udev',
    'openssl-libs', 'gnutls', 'dbus']


    Note that this list might not be exhaustive. I'd need to double-check if RedHat recommends to their paying and supported customers to restart according to this heuristic when doing unattended updates, that would give me a bit more confidence.






    share|improve this answer




















    • Quick check .. so post installing yum-utils .. need to run needs-restarting to check list of packages which require restart or reboot?
      – user227863
      Feb 8 at 19:25










    • Can we use show-installed | grep needs-restarting ?
      – user227863
      Feb 8 at 19:36














    up vote
    1
    down vote













    RHEL and derivatives have needs-restarting in the yum-utils package, but that can only give you an after-the-fact evaluation. However, it is a python script, so we can peek inside to find the following hard-coded list of packages that will make it suggest a reboot:



    # For which package updates we should recommend a reboot
    # Taken from https://access.redhat.com/solutions/27943
    REBOOTPKGS = ['kernel', 'glibc', 'linux-firmware', 'systemd', 'udev',
    'openssl-libs', 'gnutls', 'dbus']


    Note that this list might not be exhaustive. I'd need to double-check if RedHat recommends to their paying and supported customers to restart according to this heuristic when doing unattended updates, that would give me a bit more confidence.






    share|improve this answer




















    • Quick check .. so post installing yum-utils .. need to run needs-restarting to check list of packages which require restart or reboot?
      – user227863
      Feb 8 at 19:25










    • Can we use show-installed | grep needs-restarting ?
      – user227863
      Feb 8 at 19:36












    up vote
    1
    down vote










    up vote
    1
    down vote









    RHEL and derivatives have needs-restarting in the yum-utils package, but that can only give you an after-the-fact evaluation. However, it is a python script, so we can peek inside to find the following hard-coded list of packages that will make it suggest a reboot:



    # For which package updates we should recommend a reboot
    # Taken from https://access.redhat.com/solutions/27943
    REBOOTPKGS = ['kernel', 'glibc', 'linux-firmware', 'systemd', 'udev',
    'openssl-libs', 'gnutls', 'dbus']


    Note that this list might not be exhaustive. I'd need to double-check if RedHat recommends to their paying and supported customers to restart according to this heuristic when doing unattended updates, that would give me a bit more confidence.






    share|improve this answer












    RHEL and derivatives have needs-restarting in the yum-utils package, but that can only give you an after-the-fact evaluation. However, it is a python script, so we can peek inside to find the following hard-coded list of packages that will make it suggest a reboot:



    # For which package updates we should recommend a reboot
    # Taken from https://access.redhat.com/solutions/27943
    REBOOTPKGS = ['kernel', 'glibc', 'linux-firmware', 'systemd', 'udev',
    'openssl-libs', 'gnutls', 'dbus']


    Note that this list might not be exhaustive. I'd need to double-check if RedHat recommends to their paying and supported customers to restart according to this heuristic when doing unattended updates, that would give me a bit more confidence.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Feb 8 at 18:32









    Ulrich Schwarz

    8,87512643




    8,87512643











    • Quick check .. so post installing yum-utils .. need to run needs-restarting to check list of packages which require restart or reboot?
      – user227863
      Feb 8 at 19:25










    • Can we use show-installed | grep needs-restarting ?
      – user227863
      Feb 8 at 19:36
















    • Quick check .. so post installing yum-utils .. need to run needs-restarting to check list of packages which require restart or reboot?
      – user227863
      Feb 8 at 19:25










    • Can we use show-installed | grep needs-restarting ?
      – user227863
      Feb 8 at 19:36















    Quick check .. so post installing yum-utils .. need to run needs-restarting to check list of packages which require restart or reboot?
    – user227863
    Feb 8 at 19:25




    Quick check .. so post installing yum-utils .. need to run needs-restarting to check list of packages which require restart or reboot?
    – user227863
    Feb 8 at 19:25












    Can we use show-installed | grep needs-restarting ?
    – user227863
    Feb 8 at 19:36




    Can we use show-installed | grep needs-restarting ?
    – user227863
    Feb 8 at 19:36












    up vote
    0
    down vote













    Exclude a package from update : Edit /etc/yum.conf → add one or more "exclude" lines. https://tecadmin.net/exclude-packages-from-yum-update/



    exclude=kernel*


    Note : The wildcard ( * ) is important.






    share|improve this answer
























      up vote
      0
      down vote













      Exclude a package from update : Edit /etc/yum.conf → add one or more "exclude" lines. https://tecadmin.net/exclude-packages-from-yum-update/



      exclude=kernel*


      Note : The wildcard ( * ) is important.






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        Exclude a package from update : Edit /etc/yum.conf → add one or more "exclude" lines. https://tecadmin.net/exclude-packages-from-yum-update/



        exclude=kernel*


        Note : The wildcard ( * ) is important.






        share|improve this answer












        Exclude a package from update : Edit /etc/yum.conf → add one or more "exclude" lines. https://tecadmin.net/exclude-packages-from-yum-update/



        exclude=kernel*


        Note : The wildcard ( * ) is important.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 9 at 18:26









        Knud Larsen

        908137




        908137












            jQh9dl5SIcy7uzBWj3Me0flB47lhGNE
            eW Xp05DDeAr1F0qNMNJOiK7VXGrYlwAYlHV2PbT9U6Odfs81n

            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            How many registers does an x86_64 CPU actually have?

            Displaying single band from multi-band raster using QGIS