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