On Tue, 19 Feb 2013 17:02:54 +0100
Kwpolska wrote:
> On Tue, Feb 19, 2013 at 3:00 AM, Ralf Mardorf
> wrote:
> > On Tue, 19 Feb 2013 01:40:10 +0100, Tom Gundersen wrote:
> >>>
> >>> # timedatectl set-local-rtc 1
> >>> Failed to issue method call: Input/output error
> >>
> >>
> >> That message is
On Tue, Feb 19, 2013 at 3:00 AM, Ralf Mardorf
wrote:
> On Tue, 19 Feb 2013 01:40:10 +0100, Tom Gundersen wrote:
>>>
>>> # timedatectl set-local-rtc 1
>>> Failed to issue method call: Input/output error
>>
>>
>> That message is disconcerting (at least the error message should have
>> been clearer)
On Mon, 18 Feb 2013 17:50:06 +0100
"Ralf Mardorf" wrote:
> Hi :)
>
> after a reboot there always is an offset of -3600 sec, when running
> ntpdate.
>
> # timedatectl status | grep local
> RTC in local TZ: yes
> Warning: The RTC is configured to maintain time in the local time
> zone. Th
On Tue, 19 Feb 2013 01:40:10 +0100, Tom Gundersen wrote:
# timedatectl set-local-rtc 1
Failed to issue method call: Input/output error
That message is disconcerting (at least the error message should have
been clearer). Could you have a look in "journalctl" (as root) to see
if you can get more
On Mon, Feb 18, 2013 at 5:50 PM, Ralf Mardorf
wrote:
> after a reboot there always is an offset of -3600 sec, when running
> ntpdate.
>
> # timedatectl status | grep local
>RTC in local TZ: yes
> Warning: The RTC is configured to maintain time in the local time zone.
> This
>RTC in
Hi :)
after a reboot there always is an offset of -3600 sec, when running
ntpdate.
# timedatectl status | grep local
RTC in local TZ: yes
Warning: The RTC is configured to maintain time in the local time zone.
This
RTC in UTC, by calling 'timedatectl set-local-rtc 0'.
# timedatect
6 matches
Mail list logo