|Title||The replicator process is hard to manage|
|Assigned user||Gareth Rees|
|Description||The replicator process is hard to manage, especially on Windows NT, where one has to launch it using a non-trivial command line at a prompt.|
|Analysis||The replicator should be a Windows service, so that it can be managed using the standard interface, and monitored and managed using Windows network administration tools.|
On Unix, the replicator should be as much like a normal daemon as possible.
GDR 2001-06-07. Turning the P4DTI into a Windows NT service is not easy. The P4DTI is a polling service that uses sleep() to wait between polls. Windows NT services can't work like that, so the P4DTI will need to be changed to use Windows timer services. This means that we'll have to have an operating system interface. On Unix we would make the P4DTI into a daemon: sleep() is OK, but it will need to respond correctly to SIGHUP, SIGINT and so on.
See "Programming Python on Win32" for advice on writing NT services in Python.
GDR 2001-06-28. See  for some more advice.
This is Perforce job 5272.
|Created by||Richard Brooksby|
|Created on||2000-11-21 16:06:35|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 19:01:11|
|History||2000-11-21 RB Created from sources (see evidence)|
2001-06-07 GDR Added analysis.
2001-06-28 GDR Added .
2001-10-05 GDR Upgraded to essential since customers need this feature.
2001-11-13 GDR Closed (but signal handling work still needs to be done; see job000367).
|23875||closed||2001-11-09 21:13:50||Nick Levine||Merge nt-service bramch back into master sources.|