on -f3 rtc -s hw

Do I get it right, if I do the following on the 2nd node:
$ on -f3 rtc -s hw
it will set the CMOS timer on the 3rd node to the current system time on
the same 3rd node?

Tony.

Tony <mts.spb.suxx@mail.ru> wrote:

Do I get it right, if I do the following on the 2nd node:
$ on -f3 rtc -s hw
it will set the CMOS timer on the 3rd node to the current system time on
the same 3rd node?

That sounds right to me.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

On 12 Apr 2005 15:51:38 GMT, David Gibbs <dagibbs@qnx.com> wrote:

That sounds right to me.
OK.

Then doing the following on 2nd node:
$ on -n3 rtc -s hw
will set the CMOS on node 2 (i.e. local) to the current system time on
node 3 (remote), right?

Tony.

Tony <mts.spb.suxx@mail.ru> wrote:

On 12 Apr 2005 15:51:38 GMT, David Gibbs <> dagibbs@qnx.com> > wrote:
That sounds right to me.
OK.
Then doing the following on 2nd node:
$ on -n3 rtc -s hw
will set the CMOS on node 2 (i.e. local) to the current system time on
node 3 (remote), right?

Nope. It will, also, set the cmos clock on node 3, from (I think)
node 3’s system time. (The difference between -n3 and -f3 is that
in the case of -n3 /=//2 while for -f3 /=//3. For something that
writes directly to the hardware, the meaning of / is completely
irrelevant. I’m pretty sure the time lookup also doesn’t go through
the pathname space, since “on -fnode date”, and “on -nnode date” gave
the same time, which was different from “date”.)

If you want to set the CMOS clock on the local node to the system
time on node 3, you could do it with:

rtc net 3
rtc -s hw

The first sets the system time locally to the system time on node 3,
then sets the hardware time to the system time on node 2 (i.e. local).
This does have the side effect of setting the local time along the way.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

Thank you very much!

Tony.