Re: (ASCEND) M2K compliance testing

To: Jim Howard <jhoward@lyceum.com>
Subject: Re: (ASCEND) M2K compliance testing
From: Phillip Vandry <vandry@Mlink.NET>
Date: Fri, 29 May 1998 17:08:21 -0400 (EDT)
cc: ascend-users@bungi.com
In-reply-to: Your message of "Fri, 29 May 1998 16:30:00 EDT." <2.2.32.19980529203000.00ff8ad8@pop.lyceum.com>
Sender: owner-ascend-users@max.bungi.com

> strangely though, moving my clock forward two years
> doesn't seem to affect the uptime counters:
> 
> ascend% sh uptime
> system uptime: up 33 days, 8 hours, 3 minutes, 22 seconds 

Hosts, and I am assuming routers like Maxes too, measure uptime in
clock ticks since the clock was activated, so that would explain it.

Under Solaris, for instance, the kernel variable is lbolt (lightning bolts
since boot)

-Phil
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

References:

Re: (ASCEND) M2K compliance testing

From: Jim Howard <jhoward@lyceum.com>

Prev by Date: Re: (ASCEND) Multiple Radius Caller-Id Attributes or numbers possible?
Next by Date: Re: (ASCEND) Multiple Logins.
Prev by thread: Re: (ASCEND) M2K compliance testing
Next by thread: (ASCEND) v.90 release version? when?
Index(es):
- Main
- Thread