seen on fs table. Fairly often (perhaps 1 in 5 set_position calls), the newport delays will fail to report a change in current position upon moving. An independent yaqc client can verify that the daemon position does not agree with the yaqc-cmds position reading.
Setting the position a second time to the same position (effectively calling get_position again) usually fixes this.
seen on fs table. Fairly often (perhaps 1 in 5 set_position calls), the newport delays will fail to report a change in current position upon moving. An independent yaqc client can verify that the daemon position does not agree with the yaqc-cmds position reading.
Setting the position a second time to the same position (effectively calling get_position again) usually fixes this.