(19-04-2014 21:33)simoncn Wrote: (19-04-2014 21:16)MikeSpragg Wrote: Also, just noticed this in the minimserver.log
20:20:45.432 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
20:22:27.485 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.
20:30:52.122 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.
20:35:44.431 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
20:44:59.432 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.
20:45:08.535 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
20:52:52.397 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.
21:05:45.569 Thread-14: ohNet: Device 9cb06ef5-943a-41ab-8e97-a0433fa0bdc7 starting to send alive notifications.
21:11:57.496 Thread-14: ohNet: Device 0ec6be65-14bd-47e0-b5ac-25d48301fb58 starting to send alive notifications.
There are long gaps in-between - but, eventually, it updates again....
z
This is expected if you have the logging level set to Debug. For spin-down to occur, you must set the logging level to Info.
Well, that's interesting then - as it is set to Info.
MinimWatch - Properties | System | ohNet.Debug default
MinimWatch - Options | Properties - ohNet.Debug default
MinimWatch - Options | Show Log - Info
Search
Member List
Calendar
Help
