SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0000036: Change NTP from NTPDate to NTPD - MantisBT
MantisBT - Endian Firewall
View Issue Details
0000036Endian FirewallGUIpublic2006-10-02 13:542007-01-02 07:55
0000036: Change NTP from NTPDate to NTPD
I am requesting that the NTP mechanism be changed from NTPDate to NTPd. Seems kinda harsh for NTPDate to force the time every hour instead of letting NTPd adjust it as needed.
No tags attached.
Issue History
2006-10-02 13:54kfasonNew Issue
2006-10-05 23:02peter-endianNote Added: 0000055
2006-10-05 23:02peter-endianAssigned To => peter-endian
2006-10-05 23:02peter-endianStatusnew => acknowledged
2006-10-25 20:43peter-endianStatusacknowledged => resolved
2006-10-25 20:43peter-endianResolutionopen => fixed
2006-10-25 20:43peter-endianNote Added: 0000059
2007-01-02 07:55ra-endianStatusresolved => closed
2007-01-02 07:55ra-endianFixed in Version => 2.1

2006-10-05 23:02   
well, this is because the ntp restart script is not yet a python script which easily produces the ntp configuration file using cheetah.
in this manner it simply was easier for us to implement the give functionality of a ntp server, which publishes the *local* time and don't update if the user would like to keep it's own time for what reason ever.
as soon as we have cheetah templates the cron-ntpdate script will disappear, since the checkbox "dont automatically synchronize" may control the sync behaviour of ntpd.
i also planned to give the possibility to change the timezone within this cgi...
2006-10-25 20:43   
is implemented now. will be shipped with the next release