I added some preliminary checking to try to figure out if a file is the same. If it isn’t, it deletes it on the remote side, and then continues checking the other files. This means lftp should always start a fresh file.

Actually, only / got expanded using all that is available on the drive… the /home partition did not get expanded.

That’s OK though - I can work with that at least.

@Wayne-Workman Done.

I’ve patched this up in a suggested pull request. see here for details: https://forums.fogproject.org/topic/6732/install-update-your-database-blank-white-page

@pmonstad https://forums.fogproject.org/topic/6738/not-possible-to-delete-active-tasks/2#

It clearly says all tasks were active tasks. Which is it?

Added checking code to remove any package that can no longer be found.

See my post here please: https://forums.fogproject.org/topic/6781/php5-gettext

Only needs to have the -c argument once, after that it should work continuously.

@Matthieu-Jacquart Told ya.

Confirmed working. the CA ssl folders can now be separated from the snap-ins folder

@Wayne-Workman while I realize this is very old, I feel I must add, the legacy clients Config files always defaulted force reboot to off. It is this I imagine is the meaning of lazy mode.

@Sebastian-Roth I’m marking it as solved. I cannot replicate.

I set multiple systems up for ONLY All Snapin Tasks.

@Tom-Elliott Yes the settings apply through the group to the hosts in the group.

Found, confirmed, and fixed plus a little.

Snapin associations weren’t being deleted for whatever reason, so I’ve added code to ensure it will do so now.

To fix the systems that currently believe it’s already broken, we do the same thing.

I check the associations, check the valid ID’s, and delete associations that are no longer valid when compared to the two primary tables.

God’s ways are inscrutable 😳

With the new kernel works fine and with the old one no.

Close this ticket, please!!

Yeah!! Works fine

@Tom-Elliott Thanks! Works as expected. And I see the confusion regarding this bug. I didn’t report it very clearly, and you took it mean the the result of the “fog” script within the debug session vs the actual start of the task. I’ll take care to report more completely in the future. Thanks again for all your efforts here!

@Sebastian-Roth I deleted my fog repo and then pulled it down fresh. The THERE! disappeared… 😕

Guess I messed with some code previously and forgot about it. idk, I mess with a lot of stuff lol.

Confirmed found and fixed.

I want to add a caveat to this. I really don’t like relying on OS type as a defining factor. That said, 1.3.0 still relies on OS type to determine if it’s a valid resizable OS (Windows XP,Vista,7,8,8.1,10) and (Linux, Chromium OS). It also relies on the os type to determine the “fixed_size_partitions”. Of course the fixed_size_partitions file can be edited after the upload, but I am still under the impression we should really use it from the GUI. I will work on it, but for now I’m glad this is working.