Fog client weirdness
-
have you explicitly disabled the various power states? from the factory, we’ve had some computers set to disable onboard network cards to the extent that they don’t even provide link lights in the off state.
we too have our computers set to not power down or use power saving modes. they just aren’t as reliable that way, in my experience. (although, we have a couple university owned wind turbines, that counteracts the un-ethical-ness, right?) -
Works fine after doing delayed start.
But this kind of tallies with this:
[QUOTE][FONT=sans-serif][COLOR=#000000]One of the first things we try to do in mStart is to sleep for a fair amount of time if the process we are doing does not need to run right at service startup. [B]The idea behind this is that the Windows startup process can be very slow in the first place, so we don’t want the fog service to break the proverbial “Camel’s Back”.[/B][/COLOR][/FONT][/QUOTE]
[url]http://www.fogproject.org/wiki/index.php/Creating_Custom_FOG_Service_Modules[/url]
Im convinced its to do with the speed of services starting up, affected by the SSD in a system. If anyone disagrees, suggest an alternative
-
You are correct, the client currently being distributed is set to start once a core windows service does. However, this is actually too soon on faster systems as not all programs are fully initialized yet. The delayed start is an acceptable solution, or you could link the service to start when a different windows services does. This issue should be resolved with the new client when it is released
-
Ah cool, there hasn’t been a client update in a long time, right? What’s the plan for it?
