'tinj', the transient injection driver program, has not been running since Sept. 8 -- which is fine since there were no signals scheduled to be injected.  This evening I restarted it by logging into the h1hwinj1 machine (as user 'hinj'), cd'ing to /data/scirun/O1/HardwareInjection/Details/tinj/, and doing "nohup run_tinj >& nohup.out &".  So tinj is now running, but we have not YET put any new injections into the schedule.  We'll do that after checking with people that they won't interfere with other activities.