WD 3.0 users of scheduling should 'git pull'


Rob Robinett
 

There were scheduling problems in 3.0.2.5 which are corrected in 3.0.2.6


Rob Robinett
 

This morning I made further refinements to WD 3.0.2.6 to address some 'zombie kiwirecorder' issues.
That newest 3.0.2.6 has been running cleanly on about 20 servers for 2-6 hours
So I would strongly encourage the dozen or so WD users who are running 3.0.2.6 to 'git pull' it and restart their WD service.
After startup run 'wd -l e' to watch for error lines.  You may see some or many lines soon after starting it, but after that you should see no error lines reported


Chris Mackerell
 

Thanks!

The zombies appear to have been successfully driven
out of my system with the new update 😁

Cheers, Chris

On 2022-06-04 08:11, Rob Robinett wrote:
This morning I made further refinements to WD 3.0.2.6 to address some 'zombie kiwirecorder' issues.
That newest 3.0.2.6 has been running cleanly on about 20 servers for 2-6 hours
So I would strongly encourage the dozen or so WD users who are running 3.0.2.6 to 'git pull' it and restart their WD service.
After startup run 'wd -l e' to watch for error lines.  You may see some or many lines soon after starting it, but after that you should see no error lines reported