1===== timed ===== 2MAN. Limit of 30 hosts should be doc'ed. 3 4**** It should be dynamically allocated with no limit. On a large network, 5 one host could possibly master over many more than 30 hosts. That will 6 partly depend upon how the multi-network code gets implemented, but the 7 dynamic allocation can be used anyway. 8 9UGLY,CODE. timedc/cmds.c has a lots of repeated code in it. 10 11**** I haven't looked at the code, but if you want to work it over, be my 12 guest. The first thing I seem to remember is that each command is set 13 up as if it were an individual program taking argc and argv. A more 14 conventional calling style should be used. I don't think any of the 15 routines take more than a couple arguments. 16 17UGLY. fxn definition syntax does't follow convention: 18 has type on same line. 19 20**** I agree that it needs to be fixed at least enough that tags 21 will work on it. An entire cleanup might be nice later, but 22 is noncritical. 23 24LOBBY(mildly),CODE: Would be very convenient if date(1) took a 25 +-<number> argument to set the time relatively. With 26 the advent of timed it is now reasonable to synchronize 27 with WWV, which is nearly impossible to do "by hand" 28 with just an absolute date, and scripts are too slow. 29 format could be +-nn...nn.ss, where the '.' is required 30 to remove ambiguity. 31 32**** If you want to do it go ahead. It sounds useful. As far as 33 syntax goes, the normal format for the date should work just 34 fine for this. If the date is preceeded by a plus or minus, 35 the change is relative, otherwise it is absolute. 36 37CONF,not in nbsd. Makefile for m68000 doesn't work right: two modules, 38 not one, and named wrong. 39 40**** Low priority. This is a VAX distribution right now, so I'm not 41 too concerned about minor configuration problems with m68000 code. 42 We might try to get it fixed before the final tape. I won't even 43 look at it before the beta tape. 44 45*********************************************************************** 46Determine whether microseconds need to be printed in traces or are 47milliseconds accurate enough. 48 49Fix loop with two gateways sending each other settimes continuously. 50 51Fix problem with two packets while measuring time difference. 52