Bug 30196 - Time synchronisation for UCC clients
Time synchronisation for UCC clients
Status: CLOSED FIXED
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 normal
: UCC 1.0
Assigned To: Erik Damrose
Lukas Walter
: interim-4
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-29 11:10 CET by Moritz Muehlenhoff
Modified: 2013-03-26 09:14 CET (History)
0 users

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2013-01-29 11:10:33 CET
Now that use only Kerberos for authentication correct time sources are crucial for operating a UCC system.

We need to do the following:

- Configure the UCR variable timeserver (From a first glance setting it during univention-join would be best)

- Configure an Upstart job ucc-time (start on net-device-up), which runs ntpdate with the server specified in the UCR variable
Comment 1 Erik Damrose univentionstaff 2013-01-30 15:10:08 CET
ucc/timeserver is set to the dc master during univention-join. The upstart script ucc-ntpdate.conf reads this variable and sets the time while booting.
Comment 2 Lukas Walter univentionstaff 2013-01-31 16:07:57 CET
OK -> ucc/timeserver was set to the DC master after join
OK -> clocks were synchron


Verified.
Comment 3 Lukas Walter univentionstaff 2013-01-31 16:11:47 CET
(In reply to comment #2)
> OK -> ucc/timeserver was set to the DC master after join
> OK -> clocks were synchron
> 
> 
> Verified.

synchron after reboot
Comment 4 Moritz Muehlenhoff univentionstaff 2013-03-26 09:14:02 CET
UCC 1.0 has been released: 
http://forum.univention.de/viewtopic.php?f=26&t=2417
http://forum.univention.de/viewtopic.php?f=54&t=2418

If this error occurs again, please use "Clone This Bug".