Bug ID | 1204593 |
---|---|
Summary | own telegraf.service gets overwritten when OS is updated |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | aarch64 |
OS | openSUSE Tumbleweed |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Other |
Assignee | screening-team-bugs@suse.de |
Reporter | hslager@hotmail.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
After Tumbleweed OS/distro updating, telegraf fails (and failed) to get running somtimes. Reason is that an MQTT host might not be online (yet) and telegraf.service autorestarting is too fast, so then no telegraf active and failures due to that in my homeautomation. I added: RestartSec=30 in telegraf.service, after the comments line: # end of automatic additions So my expectation is: During a next update, my own modified telegraf.service stays as is. But it is actually overwritten by a newer / package provided version. A telegraf.service.rpmnew is created also, but that is quite useless if the resulting telegraf.service is the same and my own fixes get overwrittng. Solution would be to not overwrite the users modifications or at least not after a comment line that suggests that user changes after that are save. Other solution is to take my RestartSec=30 as default in the package, so others might also benefit from it.