Thanks to solve bugs so quick guys. Excellent job.

Thanks Tom. I guess you fix it in last builds. I am going to try it.

I understand why this is an issue but cannot explain why it’s happening. Especially as this seems to be a one off problem. While some systems seem to be more prone to this than others it’s still a very strange issue. Part of the strangeness of the issue is it doesn’t actually appear to affect the imaging process in any way. It ultimately is just colors. If I knew what’s causing it, and my suspicion is with the frame buffer console, I might be able to get a fix for this. Again, while I understand the issue it doesn’t appear to actually interfere with the imaging process.

OK, that makes sense. Probably snapins began too soon.
I will check that, thanks.

Thanks Tom. I didn’t pretend to criticized Fog in any way because I think it is a great tool and there is an excellent work behind it.
We think that multicast is a very good way to get the best from network bandwidth if you are sending the same image to multiple clients, so we think that a product like fog could take profit of this.
From you answer I guess that multicast is not a priority so I will follow your advise and I will try to modify code to allow multiple multicast transfers. The only thing I wanted to know it was if that was in your roadmap.

Thanks a lot anyway.

Frank

Hi again Tom,
I’ve updated to 1.1.1 and the behaviour is the same. Launching a mullticast deploy the associated snap-ins are not launched.
By the way, what is the deployment button that appears in host list for? It seems to launch a deploy of one host using multicast, but that doesn’t have much sense.
Regards.

Frank

the client software has not changed. if the ip address of the server does not change, the existing clients will talk to the new server

[quote=“Frank, post: 29117, member: 691”]Hi Tom,
Can it be that the search use snapinAssoc table and the SELECT lacks DISTINCT clause? That would explain the repetititon.
Frank[/quote]

I don’t think that’s it. If we added DISTINCT to the SELECT params, it would not allow certain search functions to work properly. I’ll take a look at the query string, if that’s even being used, for the snapin page.

Hi Tom,
finally it seems solved. But I have had to make another action to make snap-ins work. You know that there is a change in snap-in file selection; i chose it from a select list an then click on “update” to make it efective, and then you see the file in the “sap file max size” box. But after migration to 1.0.1, in that box there is the whole path of file and that makes snap-in file download fails. It is necessary to click the “update” button i all of your snap-ins to make it work fine.

I think that is so much important to advise users who are going to migrate. So my advise for them regarding to snap-ins will be:
[LIST]
[]double-check that your snap-in task tables are empty, specially if you see after migration snap-in tasks in fog console which should not be there
[]apply update on all of your snap-ins
[/LIST]
Thank you very much for your hep Tom.
I hope not to bother you more (at least in short ;))

Frank
UPC-Terrassa8Barcelona)

It is:
[code]
svn co https://svn.code.sf.net/p/freeghost/code/trunk /opt/fog_latest
cd /opt/fog_latest/bin
./installfog.sh
[/code]

Thanks a lot Tom, that solved the issues. Great!.
Excuse me if it was so obvious to ask it here.
Now it’s time to test this brand new fog version.

Best regards.

Frank
UPC - Barcelona