Red Hat Bugzilla – Bug 64471
servers time is not set correctly in linuxconf
Last modified: 2007-04-18 12:42:26 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 (Macintosh; U; PPC)
Description of problem:
when using linuxconf (date&time)
with a time server, and time set to localtime.
clicking on the accept:
however it should execute
/sbin/rdate -s [timeserver] so that the time gets set and not just
then the following command
/sbin/clock -w --localtime stores the time correctly
as it is its just storing the time that is already set, which may or may not be
correct, and defeats the whole point of the exercise.
or should the user get a message to re-boot the server to install the new time,
so that the server does not get confused , with cronjobs etc.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: time is only displayed but not set
Expected Results: time should be set, or a message asking the user to re-boot
the server to take up the new time
i have classed it as high, because if the server is not setting its time
correctly, both my backups and my oracle database are running with incorrect
info, which in the case of oracle can result in lost/corrupted data.
Closing because we don't ship linuxconf anymore
sorry that does not cut it ,as regards a valid bug.
but if you insist in taking this attitude towards valid bugs, then you can
consider your product range dropped from further use by my consultancy.
have a nice day
As stated, linuxconf is not part of our products since Red Hat Linux 7.3, so we
aren't going to fix most linuxconf bugs in older releases.