Bug 1087895 - Yast2 NTP module want chrony
Yast2 NTP module want chrony
Status: RESOLVED FEATURE
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: YaST2
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
Jiri Srain
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-03 12:40 UTC by Bruno Friedmann
Modified: 2018-04-03 13:17 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Friedmann 2018-04-03 12:40:28 UTC
Yast2 NTP ask each time to install chrony package.

ntp can run as daemon, so chrony is not useful.

if ntp is not run as daemon the scripts should use already activated systemd timers and no more cron like things.

check logrotate rpm if needed.
Comment 1 Steffen Winterfeldt 2018-04-03 12:49:27 UTC
Josef, could you have a look please?
Comment 2 Josef Reidinger 2018-04-03 12:52:49 UTC
(In reply to Bruno Friedmann from comment #0)
> Yast2 NTP ask each time to install chrony package.
> 
> ntp can run as daemon, so chrony is not useful.
> 
> if ntp is not run as daemon the scripts should use already activated systemd
> timers and no more cron like things.
> 
> check logrotate rpm if needed.

well, YaST NTP client now configures chrony as ntp client. If you use systemd timers for nto synchronization, then YaST module is not for you. ( and yes, we also use it in certain conditions ).

BTW chrony of course can also run as daemon as chronyd or single time as chronyc. We use and allow to configure both ways.

So from my POV it works as expected.

logrotate rpm is needed for YaST2 itself to rotate its logs.
Comment 3 Bruno Friedmann 2018-04-03 12:59:24 UTC
Joseph sorry I mixed anacron/cron task and chrony(d) time related task.

So you're right everything is expected from a pov of yast2/ntp module and that sense.

For myself I'm using systemd-timesyncd which work better for my usage.

I've just one remark, during installation, there's no way to escape yast ntp module configuration that I've seen, or did I missed something ?
Comment 4 Josef Reidinger 2018-04-03 13:06:57 UTC
(In reply to Bruno Friedmann from comment #3)
> Joseph sorry I mixed anacron/cron task and chrony(d) time related task.
> 
> So you're right everything is expected from a pov of yast2/ntp module and
> that sense.
> 
> For myself I'm using systemd-timesyncd which work better for my usage.
> 
> I've just one remark, during installation, there's no way to escape yast ntp
> module configuration that I've seen, or did I missed something ?

Well, I think that by default ntp sync is not enabled, unless you did it in timezone part of installation. yast2-ntp-client installation I think can be also as other yast modules also skipped ( we have some SLE15 product that do not provide any yast module for minimal system ).
About cron - ntp client also allow to configure sync via cron, but it should not force installation of cron itself. Yast just writes cron configuration file.

So you to sum it:

1. ntp does not need to be configured ( it is done in timezone screen when you click on Other settings )

2. YaST2 ntp client does not need to be installed, but by default it is installed.

Is it clear now?
Comment 5 Bruno Friedmann 2018-04-03 13:17:29 UTC
Thanks for the brief review of the process.
If anything goes not that way during leap 15 and TW test I will reopen proper bug report with yast2 log attached.

Thanks closing