I made the same experience as Adrian.
Many of us use armbian for production in Soho or as smart home appliance, so I think it should come as a proper Linux system, not Just as a development playground to be reflashed after a few days.
This behaviour basically renders htop useless, because if you have e.g. nextcloud running you only see lots of threads of one server and this have to config htop every time again, which is so annoying!
In 20 years of Debian usage I haven't seen any script messing with another packages configuration or a script rewriting all users configuration.
Clearly this should be done on a different level and setting changes made by the user
Sure we can find a better way to make this work, Here some ideas.
-Does htop handle an a include statement in its config file, so we could have this changes made in one central place?
-The relevant config options could be added at the bottom of the config files. First check for them.
I made the same experience as Adrian.
Many of us use armbian for production in Soho or as smart home appliance, so I think it should come as a proper Linux system, not Just as a development playground to be reflashed after a few days.
This behaviour basically renders htop useless, because if you have e.g. nextcloud running you only see lots of threads of one server and this have to config htop every time again, which is so annoying!
In 20 years of Debian usage I haven't seen any script messing with another packages configuration or a script rewriting all users configuration.
Clearly this should be done on a different level.
Sure we can find a better way to make this work, Here some ideas.
-Does htop know something like a include statement in its config ffile
-The relevant config options could be added at the bottom of the config files. First check for them.
I made the same experience as Adrian.
Many of us use armbian for production in Soho or as smart home appliance, so I think it should come as a proper Linux system, not Just as a development playground to be reflashed after a few days.
This behaviour basically renders htop useless, because if you have e.g. nextcloud running you only see lots of threads of one server and this have to config htop every time again, which is so annoying!
In 20 years of Debian usage I haven't seen any script messing with another packages configuration or a script rewriting all users configuration.
Clearly this should be done on a different level.
Sure we can find a better way to make this work, Here some ideas.
-Does htop know something like a include statement in its config ffile
-The relevant config options could be added at the bottom of the config files.
-maybe it helps if you just uncomment the Line #13-14
# start with a clean copy
# cp /etc/skel/.config/htop/htoprc "${homedir}"/.config/htop/htoprc