What good is it to know the alert time if you don't relate it to the =
current sysUpTime?
Bob
----------
From: Jay Martin[SMTP:jkm@underscore.com]
Sent: Thursday, November 20, 1997 12:01 PM
To: Bob Pentecost
Cc: pmp@pwg.org
Subject: Re: PMP> Justification for prtAlertTime and prtAlertTimeGrou
Bob,
Regarding the second topic of your previous reply:
> While we're on the topic of prtAlertTime, I had a question come to me =
about this object. As I had mentioned when we were changing this object =
to mandatory, the sysUpTime is kept in our Network Interface Card (the =
issue at the time was due to problems getting the time from the NIC, but =
I don't care to revisit that aspect). What's the printer to do when it =
has two such cards installed? One might argue that there's one power =
supply so the times start when the power is turned on, but the time =
could also be kept in an external NIC that communicates with the printer =
over the parallel port. Also, I'm not sure, but the clock drift between =
two NIC timers could be significant.
>=20
> Any thoughts?
Good question. I would think that the manufacturer would simply
choose one of the NICs as the "master" and use its values. As
long as the same NIC values are used, then it probably wouldn't
matter that much. (Is there any reason a client app would want
to some way coodinate the value of MIB-II's sysUpTime with a
prtAlertTime value?? Seems unlikely...)
Of course, we don't build printers, so this opinion may not be
shared with those who do.
...jay
----------------------------------------------------------------------
-- JK Martin | Email: jkm@underscore.com --
-- Underscore, Inc. | Voice: (603) 889-7000 --
-- 41C Sagamore Park Road | Fax: (603) 889-2699 --
-- Hudson, NH 03051-4915 | Web: http://www.underscore.com --
----------------------------------------------------------------------