Hi,
to get the correct system time I use ntp-client in the boot process.
Furthermore in /etc/conf.d/hwclock I set:
# Set CLOCK to "UTC" if your Hardware Clock is set to UTC (also known as
# Greenwich Mean Time). If that clock is set to the local time, then
# set CLOCK to "local". N
On Mon, Feb 6, 2012 at 12:51 PM, wrote:
> Hi,
>
> to get the correct system time I use ntp-client in the boot process.
> Furthermore in /etc/conf.d/hwclock I set:
>
> # Set CLOCK to "UTC" if your Hardware Clock is set to UTC (also known as
> # Greenwich Mean Time). If that clock is set to
Michael Mol [12-02-06 19:20]:
> On Mon, Feb 6, 2012 at 12:51 PM, wrote:
> > Hi,
> >
> > to get the correct system time I use ntp-client in the boot process.
> > Furthermore in /etc/conf.d/hwclock I set:
> >
> > # Set CLOCK to "UTC" if your Hardware Clock is set to UTC (also known as
> > #
meino.cra...@gmx.de wrote:
> Hi,
>
> to get the correct system time I use ntp-client in the boot process.
> Furthermore in /etc/conf.d/hwclock I set:
>
> # Set CLOCK to "UTC" if your Hardware Clock is set to UTC (also known as
> # Greenwich Mean Time). If that clock is set to the local t
On Mon, Feb 6, 2012 at 1:39 PM, wrote:
> Michael Mol [12-02-06 19:20]:
>> On Mon, Feb 6, 2012 at 12:51 PM, wrote:
>> > Hi,
>> >
>> > to get the correct system time I use ntp-client in the boot process.
>> > Furthermore in /etc/conf.d/hwclock I set:
>> >
>> > # Set CLOCK to "UTC" if your Har
On Mon, Feb 6, 2012 at 1:46 PM, Dale wrote:
> meino.cra...@gmx.de wrote:
>> Hi,
>>
>> to get the correct system time I use ntp-client in the boot process.
>> Furthermore in /etc/conf.d/hwclock I set:
>>
>> # Set CLOCK to "UTC" if your Hardware Clock is set to UTC (also known as
>> # Greenw
Am 06.02.2012 19:39, schrieb meino.cra...@gmx.de:
> Michael Mol [12-02-06 19:20]:
>> On Mon, Feb 6, 2012 at 12:51 PM, wrote:
>>> Hi,
>>>
>>> to get the correct system time I use ntp-client in the boot process.
>>> Furthermore in /etc/conf.d/hwclock I set:
>>>
>>># Set CLOCK to "UTC" if your
Michael Mol [12-02-06 19:56]:
> On Mon, Feb 6, 2012 at 1:39 PM, wrote:
> > Michael Mol [12-02-06 19:20]:
> >> On Mon, Feb 6, 2012 at 12:51 PM, wrote:
> >> > Hi,
> >> >
> >> > to get the correct system time I use ntp-client in the boot process.
> >> > Furthermore in /etc/conf.d/hwclock I set:
Florian Philipp [12-02-06 20:00]:
> Am 06.02.2012 19:39, schrieb meino.cra...@gmx.de:
> > Michael Mol [12-02-06 19:20]:
> >> On Mon, Feb 6, 2012 at 12:51 PM, wrote:
> >>> Hi,
> >>>
> >>> to get the correct system time I use ntp-client in the boot process.
> >>> Furthermore in /etc/conf.d/hwcloc
meino.cra...@gmx.de wrote:
>
> As I wrote the kernel is configured
>
>
> CONFIG_RTC_HCTOSYS=y
> CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
>
> so there is no module, the functionality is compiled into the kernel.
>
> And as I wrote I am using the ntp_client to set the system time via
On Feb 6, 2012 7:00 PM, wrote:
>
> Michael Mol [12-02-06 19:56]:
> > On Mon, Feb 6, 2012 at 1:39 PM, wrote:
> > > Michael Mol [12-02-06 19:20]:
> > >> On Mon, Feb 6, 2012 at 12:51 PM, wrote:
> > >> > Hi,
> > >> >
> > >> > to get the correct system time I use ntp-client in the boot
process.
>
On Tuesday 07 February 2012 00:23:43 Dale wrote:
> Note: Use ! to comment instead of #. Weird. Command to find closest
> servers:
You don't have to. Chrony's convention is to use # for its own comments and
! for assignments you want to comment out. Just a convention though. Use
either at wi
Peter Humphrey wrote:
> On Tuesday 07 February 2012 00:23:43 Dale wrote:
>
>
>
>> Note: Use ! to comment instead of #. Weird. Command to find closest
>
>> servers:
>
>
>
> You don't have to. Chrony's convention is to use # for its own comments
> and ! for assignments you want to comment ou
>> Is your RTC driver compiled into the kernel?
> CONFIG_RTC_HCTOSYS=y
> CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
Those have nothing to do with the RTC *driver*.
AFAIK on a PC the relevant option is
CONFIG_RTC_DRV_CMOS
andrea
14 matches
Mail list logo
