Re: Announcements for manual configuration intervention?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



在 2021-04-12星期一的 21:59 +0300,Matti Pulkkinen写道:
> Hello!
> 
> TL;DR is there a list where announcements are made regarding
> configuration changes requiring manual intervention? 
> 
> Today I noticed that the clock in my Fedora 33 workstation install
> was
> about five minutes fast. Some examination revealed that none of the
> sources chrony was using for NTP were working. There was, however, a
> new configuration file, /etc/chrony.conf.rpmnew, which changed the
> sources from specific IP addresses to a pool URL. It would have been
It should be using a pool URL for a long time.
> nice if there was some kind of notification that the current chrony
> configuration is broken, and it can't be fixed automatically. Is
> there
I think it's not due to a broken configuration, maybe a broken NTP
server is specified? Can you diff those two configurations?
> a list, or some other method, by which I could be notified of these
> sorts of things? Not for specific packages necessarily, but just in
> general, even if it is high-traffic?
IIRC dnf will give you a message during upgrading. And configuration
file change may be too frequent that setting a mailing list will not be
that helpful. 

After all, if you don't touch those configurations, rpm will upgrade
them like its doing with other files, even when they are marked as
%config(noreplace). 

To avoid this, keep tracking on config files you changed, look at
outputs during update, or avoid changing them at all (if possible, use
/etc/xxx.d/xxx.conf instead).
> 
> -- 
> Terveisin / Regards,
> Matti Pulkkinen
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-
> US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproje
> ct.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

Attachment: signature.asc
Description: This is a digitally signed message part

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux