| Summary: | net-misc/chrony - add pkg_config() | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Enrico Tagliavini <enrico.tagliavini> |
| Component: | Current packages | Assignee: | Jeroen Roovers (RETIRED) <jer> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | CC: | r3pek |
| Priority: | Normal | Keywords: | PATCH |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | add emerge --config to chrony | ||
Newer ebuilds install configuration files into /etc/chrony. They're quite usable, too. (In reply to Jeroen Roovers from comment #1) > Newer ebuilds install configuration files into /etc/chrony. They're quite > usable, too. Agree, the current version has comments in the config file and is quite a lot more usable that earlier versions. |
Created attachment 345584 [details, diff] add emerge --config to chrony chrony comes with no default configuration, just the example. It is not really quick to get it working. With this patch I tried to get it ready quicker via emerge --config chrony. A default working config is not trivial, so I think an interactive, simple, emerge --config is better then shipping a static config file. This doesn't mean it will cover all cases, but it can be extended. What this patch does: - asks the user for confirmation, it will overwrite the config file - will ask if the RTC is on UTC - will ask if the computer is always connected to the internet [more on this later] - will generate a new password from /dev/urandom and will write it to /etc/chrony/chrony.keys - will generate a basic [but working out of the box.... hopefully] chrony.conf about the always connected to internet: this is very useful configuration for laptops. But without an automated way to tell chronyd when the pc os online/offline it is not very useful. I added to the ebuild a NetworkManager script that does everything automatically. With conf.d/net{,work} I have no idea if this can be done and how. What do you think about this solution? [Hopefully this time the patch is not borked, but if it is, it is surely git fault ;)]