[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problems with 32 bit Jessie and Mate DE



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Jun 20, 2015 at 09:53:47AM +0000, Curt wrote:
> On 2015-06-19, Nick <nmb@nickbooker.uk> wrote:
> > On 17/06/15 17:56, Curt wrote:
> >> That's strange; I always thought you had to set the hardware clock
> >> (hwclock) for the modified date and time to survive a reboot.
> >> 
> >> 
> >
> > I always thought the current time on the system clock was saved back to
> > the hardware clock again during shutdown too.
> >
> >
> 
> Not according to the wiki here:
> https://wiki.debian.org/DateTime

FWIW, this is extracted from my /etc/init.d/hwclock.sh:

#!/bin/sh
# hwclock.sh    Set and adjust the CMOS clock.
#
# Version:      @(#)hwclock.sh  2.00  14-Dec-1998  miquels@cistron.nl
 | [...]
 |     case "$1" in
 |         start)
 |             [...]
 |             ;;
 |         stop|restart|reload|force-reload)
 |             #
 |             # Updates the Hardware Clock with the System Clock time.
 |             # This will *override* any changes made to the Hardware Clock.
 |             #
 |             # WARNING: If you disable this, any changes to the system
 |             #          clock will not be carried across reboots.
 |             #
 |             [...]

And the script is linked in /etc/rc[06].d to stop. So with SysV, at
least, things are set up to update the hwclock at shutdown.

Don't know how things are in the Brave New Systemd World, though.

- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlWFVs4ACgkQBcgs9XrR2kanBgCeJGiNNUpx87KFWD8C8kh+Zesx
S/EAn0c2Iw7eCdK4nP4IHQfNoiIjbTcI
=8Box
-----END PGP SIGNATURE-----


Reply to: