From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Tue, 4 Aug 2009 06:56:51 +0100 Message-ID: From: roger peppe To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [9fans] more time amusement under vmware Topicbox-Message-UUID: 378baa8c-ead5-11e9-9d60-3106f5b1d025 the time problem i was having before (fast clock) had seemed to be irreproducible. however just now, i noticed the following odd behaviour: fiddle% date -u Thu Jan 1 00:00:00 GMT 1970 fiddle% cat /dev/time 0 0 0 1 fiddle% fiddle% # wait a few seconds fiddle% cat /dev/time 0 0 0 1 fiddle% the clock is completely stopped! (although sleep doesn't sleep forever - sleep 10 sleeps for about 3.43 seconds, so *something* has a concept of time) most odd. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 4 Aug 2009 05:48:21 -0700 Message-ID: <3e1162e60908040548q4381bed7off8e967958781179@mail.gmail.com> From: David Leimbach To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000e0cd6a8f2300f360470504db6 Subject: Re: [9fans] more time amusement under vmware Topicbox-Message-UUID: 37fb9e0a-ead5-11e9-9d60-3106f5b1d025 --000e0cd6a8f2300f360470504db6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Mon, Aug 3, 2009 at 10:56 PM, roger peppe wrote: > the time problem i was having before (fast clock) had seemed to be > irreproducible. however just now, i noticed the following > odd behaviour: > > fiddle% date -u > Thu Jan 1 00:00:00 GMT 1970 > fiddle% cat /dev/time > 0 0 0 > 1 fiddle% > fiddle% # wait a few seconds > fiddle% cat /dev/time > 0 0 0 > 1 fiddle% > > the clock is completely stopped! > (although sleep doesn't sleep forever - sleep 10 sleeps > for about 3.43 seconds, so *something* has a concept of time) > > most odd. > > Yeah.. :-( Odd and crappy. I can't figure out why this would happen. --000e0cd6a8f2300f360470504db6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, Aug 3, 2009 at 10:56 PM, roger p= eppe <rogpeppe@g= mail.com> wrote:
the time problem i was having before (fast clock) had seemed to be
irreproducible. however just now, i noticed the following
odd behaviour:

fiddle% date -u
Thu Jan =A01 00:00:00 GMT 1970
fiddle% cat /dev/time
=A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 0
=A0 =A0 1 fiddle%
fiddle% # wait a few seconds
fiddle% cat /dev/time
=A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 0
=A0 =A0 1 fiddle%

the clock is completely stopped!
(although sleep doesn't sleep forever - sleep 10 sleeps
for about 3.43 seconds, so *something* has a concept of time)

most odd.



Yeah.. :-( =A0Odd and crappy. = =A0I can't figure out why this would happen.
--000e0cd6a8f2300f360470504db6-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <65dceb870025dce376745cdfc6de4518@quanstro.net> From: erik quanstrom Date: Tue, 4 Aug 2009 08:54:12 -0400 To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] more time amusement under vmware Topicbox-Message-UUID: 37ffcd04-ead5-11e9-9d60-3106f5b1d025 > fiddle% date -u > Thu Jan 1 00:00:00 GMT 1970 > fiddle% cat /dev/time > 0 0 0 > 1 fiddle% > fiddle% # wait a few seconds > fiddle% cat /dev/time > 0 0 0 > 1 fiddle% what's especially wrong about this is that /bin/time is supposed to have 4 fields: ; cat /dev/time;echo 1249390400 1249390400255704909 10724776694552845 2000102324 ; do you have something funny bound on /dev? - erik From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <65dceb870025dce376745cdfc6de4518@quanstro.net> References: <65dceb870025dce376745cdfc6de4518@quanstro.net> Date: Tue, 4 Aug 2009 14:36:16 +0100 Message-ID: From: roger peppe To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] more time amusement under vmware Topicbox-Message-UUID: 38040270-ead5-11e9-9d60-3106f5b1d025 2009/8/4 erik quanstrom : >> fiddle% cat /dev/time >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0 >> =C2=A0 =C2=A0 =C2=A01 fiddle% > what's especially wrong about this is that /bin/time is supposed > to have 4 fields: it does - it just that the line wrapped. the value of the last field is 1. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <65dceb870025dce376745cdfc6de4518@quanstro.net> References: <65dceb870025dce376745cdfc6de4518@quanstro.net> Date: Tue, 4 Aug 2009 14:46:13 +0100 Message-ID: From: roger peppe To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] more time amusement under vmware Topicbox-Message-UUID: 380a07ec-ead5-11e9-9d60-3106f5b1d025 2009/8/4 erik quanstrom : > do you have something funny bound on /dev? having said what i said - yes, i realise that a mistaken bind -b means that i was using drawterm's /dev/time, not the host system's. and, oddly, drawterm implements the time file, but doesn't bother to actually get the correct time of day. so not as strange as i thought. cheers erik. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 4 Aug 2009 08:20:04 -0700 Message-ID: <13426df10908040820y787f64d0y3ac653b3d199a1b0@mail.gmail.com> From: ron minnich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] more time amusement under vmware Topicbox-Message-UUID: 38221382-ead5-11e9-9d60-3106f5b1d025 This is the same kind of problem I had under Xen in the beginning. The fix is to figure out what vmware gives you in the way of time info and use that exclusively. It problem seems odd but you can have cases where, e.g., 'sleep 10' works and date is not right. I had this under both lguest and xen. It's been enough years that I have forgotten but you also want to stop using the emulated pc-style timer interrupts. It's clear that vmware is not exactly getting these right. A look at the xen port might give some hints. Just figure out if vmware gives you a nice "time of universe" 64-bit counter or something and take your time from that. Or, alternatively, stop using vmware :-) That strikes me as the best bet. ron From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <13426df10908040820y787f64d0y3ac653b3d199a1b0@mail.gmail.com> References: <13426df10908040820y787f64d0y3ac653b3d199a1b0@mail.gmail.com> Date: Tue, 4 Aug 2009 08:20:36 -0700 Message-ID: <13426df10908040820p789419f4h482f79718a689232@mail.gmail.com> From: ron minnich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] more time amusement under vmware Topicbox-Message-UUID: 381a2f3c-ead5-11e9-9d60-3106f5b1d025 On Tue, Aug 4, 2009 at 8:20 AM, ron minnich wrote: > It problem probably sorry ron