Skip to content

Kevin

← CloudLinux UserVoice has been deprecated as of March 1st, 2023

My feedback

2 results found

  1. wrap cPanel/DA background tasks (daily backup, updates, stats etc) in LVE

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Kevin supported this idea  · 

  2. Create a lsapi.conf.rpmnew after updating package to get new config variables.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Kevin supported this idea  · 
    An error occurred while saving the comment
    Kevin commented  · 

    I would +10 this for *all* config files altered by yum upgrades

    Reason, it can start to get very challenging to keep track of changes to configs that are pushed via yum with no changelogs to support the change, (especially a problem if you enforce standard configuration using tools like puppet / chef / ansible, you can if not very careful have old configs running with new software that then causes end user issues ) , creating a rpmnew file and overwriting the old rpmnew file would make things for us 'end users' of cloudlinux much simpler.

Feedback and Knowledge Base

(thinking…)