Daylight saving in Debian 9

I would like to know how to enable Daylight saving support for Debian 9 with LXDE. My timezone is set to Europe/Rome. However my clock is one hour ahead and - considering Daylight saving - it shouldn't.

Running date from the terminal I get:

Mon 25 Feb 11:30:40 CET 2019

With date --utc:

Mon 25 Feb 10:30:40 UTC 2019

Correct UTC time from https://time.is/it/UTC should be:

Mon 25 Feb 09:30:40 UTC 2019

asked Feb 25 at 9:34

matteobin

Dual booting with Windows, not using NTP or NTP blocked in firewall?

– Rui F Ribeiro
Feb 25 at 9:56

@RuiFRibeiro Yes, I'm dual booting with Windows. I just noticed that ntpdate is not working and it gives me this error ntpdate[2883]: no servers can be used, exiting. Moreover the Bios was set to the result of date --utc. I changed it to correct UTC. Now I've got correct time, but at startup Linux said something about hardware clock being incorrect.

– matteobin
Feb 25 at 10:10

ntpdate shows that message by default if I am not wrong. You will have the time problem each time you come from Windows....does installing chrony fixes your time?

– Rui F Ribeiro
Feb 25 at 10:16

@RuiFRibeiro I don't know how chrony works. I'll try to read some docs. I'll let you know. Thanks for now.

– matteobin
Feb 25 at 10:25

add a comment |

Running date from the terminal I get:

Mon 25 Feb 11:30:40 CET 2019

With date --utc:

Mon 25 Feb 10:30:40 UTC 2019

Correct UTC time from https://time.is/it/UTC should be:

Mon 25 Feb 09:30:40 UTC 2019

asked Feb 25 at 9:34

matteobin

Dual booting with Windows, not using NTP or NTP blocked in firewall?

– Rui F Ribeiro
Feb 25 at 9:56

@RuiFRibeiro Yes, I'm dual booting with Windows. I just noticed that ntpdate is not working and it gives me this error ntpdate[2883]: no servers can be used, exiting. Moreover the Bios was set to the result of date --utc. I changed it to correct UTC. Now I've got correct time, but at startup Linux said something about hardware clock being incorrect.

– matteobin
Feb 25 at 10:10

ntpdate shows that message by default if I am not wrong. You will have the time problem each time you come from Windows....does installing chrony fixes your time?

– Rui F Ribeiro
Feb 25 at 10:16

@RuiFRibeiro I don't know how chrony works. I'll try to read some docs. I'll let you know. Thanks for now.

– matteobin
Feb 25 at 10:25

add a comment |

Running date from the terminal I get:

Mon 25 Feb 11:30:40 CET 2019

With date --utc:

Mon 25 Feb 10:30:40 UTC 2019

Correct UTC time from https://time.is/it/UTC should be:

Mon 25 Feb 09:30:40 UTC 2019

asked Feb 25 at 9:34

matteobin

Running date from the terminal I get:

Mon 25 Feb 11:30:40 CET 2019

With date --utc:

Mon 25 Feb 10:30:40 UTC 2019

Correct UTC time from https://time.is/it/UTC should be:

Mon 25 Feb 09:30:40 UTC 2019

debian date lxde ntp timezone

asked Feb 25 at 9:34

matteobin

asked Feb 25 at 9:34

matteobin

asked Feb 25 at 9:34

matteobin

asked Feb 25 at 9:34

matteobin

asked Feb 25 at 9:34

matteobin

Dual booting with Windows, not using NTP or NTP blocked in firewall?

– Rui F Ribeiro
Feb 25 at 9:56

@RuiFRibeiro Yes, I'm dual booting with Windows. I just noticed that ntpdate is not working and it gives me this error ntpdate[2883]: no servers can be used, exiting. Moreover the Bios was set to the result of date --utc. I changed it to correct UTC. Now I've got correct time, but at startup Linux said something about hardware clock being incorrect.

– matteobin
Feb 25 at 10:10

ntpdate shows that message by default if I am not wrong. You will have the time problem each time you come from Windows....does installing chrony fixes your time?

– Rui F Ribeiro
Feb 25 at 10:16

@RuiFRibeiro I don't know how chrony works. I'll try to read some docs. I'll let you know. Thanks for now.

– matteobin
Feb 25 at 10:25

add a comment |

Dual booting with Windows, not using NTP or NTP blocked in firewall?

– Rui F Ribeiro
Feb 25 at 9:56

@RuiFRibeiro Yes, I'm dual booting with Windows. I just noticed that ntpdate is not working and it gives me this error ntpdate[2883]: no servers can be used, exiting. Moreover the Bios was set to the result of date --utc. I changed it to correct UTC. Now I've got correct time, but at startup Linux said something about hardware clock being incorrect.

– matteobin
Feb 25 at 10:10

ntpdate shows that message by default if I am not wrong. You will have the time problem each time you come from Windows....does installing chrony fixes your time?

– Rui F Ribeiro
Feb 25 at 10:16

@RuiFRibeiro I don't know how chrony works. I'll try to read some docs. I'll let you know. Thanks for now.

– matteobin
Feb 25 at 10:25

Dual booting with Windows, not using NTP or NTP blocked in firewall?

– Rui F Ribeiro
Feb 25 at 9:56

@RuiFRibeiro Yes, I'm dual booting with Windows. I just noticed that ntpdate is not working and it gives me this error ntpdate[2883]: no servers can be used, exiting. Moreover the Bios was set to the result of date --utc. I changed it to correct UTC. Now I've got correct time, but at startup Linux said something about hardware clock being incorrect.

– matteobin
Feb 25 at 10:10

ntpdate shows that message by default if I am not wrong. You will have the time problem each time you come from Windows....does installing chrony fixes your time?

– Rui F Ribeiro
Feb 25 at 10:16

@RuiFRibeiro I don't know how chrony works. I'll try to read some docs. I'll let you know. Thanks for now.

– matteobin
Feb 25 at 10:25

add a comment |

1 Answer
1

active

oldest

votes

First: there is no Daylight saving time in Winter in Europe, so your question is probably not about DST, but the difference between local time and UTC.

Many Linux distributions will store the time in the system's builtin Real Time Clock (RTC) at the halt/reboot phase and read it at boot.

Below, 1. is probably not used anymore, so if not sure try 2. first.

Usually this was done with the hwclock command. This command on first usage, will create the file /etc/adjtime and among other values, store an information: if the RTC is to be considered as UTC or local time. UTC is probably the default, since it has always been the time Unix cares about, keeping UTC internally, computing localtime from UTC when needed. Now since at least historically Windows was using local time, it stores local time on the RTC. So if the wrong default for your use case (dual boot) was chosen, you could have altered it with (after correcting time):
```
hwclock --systohc --localtime
```
The way /etc/adjtime is used anyway (clock drift correction...), it's best to delete this file before having changed the time and using this command (which will recreate it).

Today, with systemd attempting to cover all bases, systemd also provides tools for setting time. So the modern equivalent which also uses /etc/adjtime should be instead:
```
timedatectl --adjust-system-clock set-local-rtc 1
```
This will re-read the RTC but consider it to be local time and also save the setting.

All this doesn't prevent you to use ntpdate (one shot sync) and chronyd (or ntpd or openntpd ...) to synchronise time with precise sources.

edited Feb 25 at 20:13

answered Feb 25 at 20:01

A.B

5,3421829

add a comment |

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f502819%2fdaylight-saving-in-debian-9%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

First: there is no Daylight saving time in Winter in Europe, so your question is probably not about DST, but the difference between local time and UTC.

Many Linux distributions will store the time in the system's builtin Real Time Clock (RTC) at the halt/reboot phase and read it at boot.

Below, 1. is probably not used anymore, so if not sure try 2. first.

Usually this was done with the hwclock command. This command on first usage, will create the file /etc/adjtime and among other values, store an information: if the RTC is to be considered as UTC or local time. UTC is probably the default, since it has always been the time Unix cares about, keeping UTC internally, computing localtime from UTC when needed. Now since at least historically Windows was using local time, it stores local time on the RTC. So if the wrong default for your use case (dual boot) was chosen, you could have altered it with (after correcting time):
```
hwclock --systohc --localtime
```
The way /etc/adjtime is used anyway (clock drift correction...), it's best to delete this file before having changed the time and using this command (which will recreate it).

Today, with systemd attempting to cover all bases, systemd also provides tools for setting time. So the modern equivalent which also uses /etc/adjtime should be instead:
```
timedatectl --adjust-system-clock set-local-rtc 1
```
This will re-read the RTC but consider it to be local time and also save the setting.

All this doesn't prevent you to use ntpdate (one shot sync) and chronyd (or ntpd or openntpd ...) to synchronise time with precise sources.

edited Feb 25 at 20:13

answered Feb 25 at 20:01

A.B

5,3421829

add a comment |

First: there is no Daylight saving time in Winter in Europe, so your question is probably not about DST, but the difference between local time and UTC.

Many Linux distributions will store the time in the system's builtin Real Time Clock (RTC) at the halt/reboot phase and read it at boot.

Below, 1. is probably not used anymore, so if not sure try 2. first.

Usually this was done with the hwclock command. This command on first usage, will create the file /etc/adjtime and among other values, store an information: if the RTC is to be considered as UTC or local time. UTC is probably the default, since it has always been the time Unix cares about, keeping UTC internally, computing localtime from UTC when needed. Now since at least historically Windows was using local time, it stores local time on the RTC. So if the wrong default for your use case (dual boot) was chosen, you could have altered it with (after correcting time):
```
hwclock --systohc --localtime
```
The way /etc/adjtime is used anyway (clock drift correction...), it's best to delete this file before having changed the time and using this command (which will recreate it).

Today, with systemd attempting to cover all bases, systemd also provides tools for setting time. So the modern equivalent which also uses /etc/adjtime should be instead:
```
timedatectl --adjust-system-clock set-local-rtc 1
```
This will re-read the RTC but consider it to be local time and also save the setting.

All this doesn't prevent you to use ntpdate (one shot sync) and chronyd (or ntpd or openntpd ...) to synchronise time with precise sources.

edited Feb 25 at 20:13

answered Feb 25 at 20:01

A.B

5,3421829

add a comment |

First: there is no Daylight saving time in Winter in Europe, so your question is probably not about DST, but the difference between local time and UTC.

Many Linux distributions will store the time in the system's builtin Real Time Clock (RTC) at the halt/reboot phase and read it at boot.

Below, 1. is probably not used anymore, so if not sure try 2. first.

Usually this was done with the hwclock command. This command on first usage, will create the file /etc/adjtime and among other values, store an information: if the RTC is to be considered as UTC or local time. UTC is probably the default, since it has always been the time Unix cares about, keeping UTC internally, computing localtime from UTC when needed. Now since at least historically Windows was using local time, it stores local time on the RTC. So if the wrong default for your use case (dual boot) was chosen, you could have altered it with (after correcting time):
```
hwclock --systohc --localtime
```
The way /etc/adjtime is used anyway (clock drift correction...), it's best to delete this file before having changed the time and using this command (which will recreate it).

Today, with systemd attempting to cover all bases, systemd also provides tools for setting time. So the modern equivalent which also uses /etc/adjtime should be instead:
```
timedatectl --adjust-system-clock set-local-rtc 1
```
This will re-read the RTC but consider it to be local time and also save the setting.

All this doesn't prevent you to use ntpdate (one shot sync) and chronyd (or ntpd or openntpd ...) to synchronise time with precise sources.

edited Feb 25 at 20:13

answered Feb 25 at 20:01

A.B

5,3421829

First: there is no Daylight saving time in Winter in Europe, so your question is probably not about DST, but the difference between local time and UTC.

Many Linux distributions will store the time in the system's builtin Real Time Clock (RTC) at the halt/reboot phase and read it at boot.

Below, 1. is probably not used anymore, so if not sure try 2. first.

Usually this was done with the hwclock command. This command on first usage, will create the file /etc/adjtime and among other values, store an information: if the RTC is to be considered as UTC or local time. UTC is probably the default, since it has always been the time Unix cares about, keeping UTC internally, computing localtime from UTC when needed. Now since at least historically Windows was using local time, it stores local time on the RTC. So if the wrong default for your use case (dual boot) was chosen, you could have altered it with (after correcting time):
```
hwclock --systohc --localtime
```
The way /etc/adjtime is used anyway (clock drift correction...), it's best to delete this file before having changed the time and using this command (which will recreate it).

Today, with systemd attempting to cover all bases, systemd also provides tools for setting time. So the modern equivalent which also uses /etc/adjtime should be instead:
```
timedatectl --adjust-system-clock set-local-rtc 1
```
This will re-read the RTC but consider it to be local time and also save the setting.

All this doesn't prevent you to use ntpdate (one shot sync) and chronyd (or ntpd or openntpd ...) to synchronise time with precise sources.

edited Feb 25 at 20:13

answered Feb 25 at 20:01

A.B

5,3421829

edited Feb 25 at 20:13

answered Feb 25 at 20:01

A.B

5,3421829

answered Feb 25 at 20:01

A.B

5,3421829

answered Feb 25 at 20:01

A.B

5,3421829

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

搜尋此網誌

mjhjmtu