Latest Development FOG

[George]

Hi Tom

Thanks for the fast answer
I have made a partirtition the whole disk and formated with ntfs. Now partclone starts, images the boot partition but it fails to image the second.

As i can see it fails to delete the partitions and partclone images only the first one.
I have made all tests with virtualbox.

[George]

Hi Tom

I am uploading a video capture from virtualbox so you can see what is happening exactly.

Thanks and sorry for my bad english

[url=“/_imported_xf_attachments/1/1989_Windows764.webm.zip?:”]Windows764.webm.zip[/url]

[Wayne Workman]

[quote=“Bill Rice, post: 47154, member: 927”]
Prior to updates - 1.8-9 Gig/min
After updates - 7.5Gig/min
[/quote]

[B]JUNKHACKER[/B] is [B]amazing[/B].

[George]

Hi

I have tested with 3347 in a different server and it is doing the same thing

[need2]

You should try again with svn 3400+. Changes were made to partition handling.

[George]

I have tried with svn 3407 and same thing happens.
Does anyone else experienced the same problem.

[Wayne Workman]

[quote=“George, post: 47495, member: 1565”]I have tried with svn 3407 and same thing happens.
Does anyone else experienced the same problem.[/quote]

Can you create a new thread with all pertaining details of your problem?

[TheKoR]

REV 3412 : loose of download speed

[Tom Elliott]

@TheKoR said:

REV 3412 : loose of download speed

We haven’t changed anything in the speed department. So if there’s a loss of speed in download/upload, maybe check the network or hardware within the machine?

[TheKoR]

All my test are done with the same machine (latitude d630) same place on my network.

Before junkhacker change i have 8/8.5 Go/min, with 3405 i have 9/10Go/min and with 3412 i have 6.5/Go/min

Edit : solved by reboot !

[Tom Elliott]

@TheKoR said:

All my test are done with the same machine (latitude d630) same place on my network.

Before junkhacker change i have 8/8.5 Go/min, with 3405 i have 9/10Go/min and with 3412 i have 6.5/Go/min

I realize that, but I still have not made any changes. If 3405 worked, and 3412 is slow, it’s something in your environment.

You can see the commits:
http://sourceforge.net/p/freeghost/code/commit_browser

I have not made a change to the init’s since: SVN 3399

[ch3i]

Hi,

I’ve tested the bandwith speed in SVN 3377 and 3412, for that image :

-rwxrwxrwx 1 root root 512 mai 18 12:57 d1.mbr
-rwxrwxrwx 1 root root 0 mai 18 12:57 d1.original.swapuuids
-rwxrwxrwx 1 root root 8620391 mai 18 12:57 d1p1.img
-rwxrwxrwx 1 root root 40917364300 mai 18 13:16 d1p2.img
-rwxrwxrwx 1 root root 3947741 mai 18 13:16 d1p3.img

In 3377 :

DL : 7.3G/Min (Avg)

In 3412:

DL : 7.4G/Min (Avg)

Regards,
Ch3i.

[Bill Rice]

@ch3i said:

Hi,

I’ve tested the bandwith speed in SVN 3377 and 3412, for that image :

-rwxrwxrwx 1 root root 512 mai 18 12:57 d1.mbr
-rwxrwxrwx 1 root root 0 mai 18 12:57 d1.original.swapuuids
-rwxrwxrwx 1 root root 8620391 mai 18 12:57 d1p1.img
-rwxrwxrwx 1 root root 40917364300 mai 18 13:16 d1p2.img
-rwxrwxrwx 1 root root 3947741 mai 18 13:16 d1p3.img

In 3377 :

DL : 7.3G/Min (Avg)

In 3412:

DL : 7.4G/Min (Avg)

Regards,
Ch3i.

As far as i know the speed increased prior to SVN 3377 (I think around 3374) and the speed you see appears to be full (again it depends on the hardware, memory, hdd and ethernet to server.) but your speeds look a lot better then the before for me… i was pulling images at 3-4Gig/min no I get about 7-7.5/gig min

[ch3i]

@Bill-Rice said:

@ch3i said:

Hi,

I’ve tested the bandwith speed in SVN 3377 and 3412, for that image :

-rwxrwxrwx 1 root root 512 mai 18 12:57 d1.mbr
-rwxrwxrwx 1 root root 0 mai 18 12:57 d1.original.swapuuids
-rwxrwxrwx 1 root root 8620391 mai 18 12:57 d1p1.img
-rwxrwxrwx 1 root root 40917364300 mai 18 13:16 d1p2.img
-rwxrwxrwx 1 root root 3947741 mai 18 13:16 d1p3.img

In 3377 :

DL : 7.3G/Min (Avg)

In 3412:

DL : 7.4G/Min (Avg)

Regards,
Ch3i.

As far as i know the speed increased prior to SVN 3377 (I think around 3374) and the speed you see appears to be full (again it depends on the hardware, memory, hdd and ethernet to server.) but your speeds look a lot better then the before for me… i was pulling images at 3-4Gig/min no I get about 7-7.5/gig min

It was to check if I had the same problem than TheKoR

Regards,
Ch3i.

[George]

Hi

Thanks Tom for the fix everything is working as should be with the latest version.
Something else you don t need to apologies to anyone. You are doing a great job and everyone should be patient.

Again thanks everyone that have helped to make this project.

[Tom Elliott]

SVN 3633 released.

I know it’s been a while since I last updated this area, but you all are likely aware of most of the changes.

This release, and for the last few revisions, I’ve been making strides in commonizing the functions for the installer.

If you haven’t been paying much attention, I’ve added a few features to this installer.

You can now use your own config file rather than only with the /opt/fog/.fogsettings. It will default back to this file.

The Options listing:

Usage: ./installfog.sh -[hdUuHSCKY] -[f <filename>]
        -h -? --help                    Display this info
        -d    --no-defaults             Don't guess defaults
        -U    --no-upgrade              Don't attempt to upgrade
        -H    --no-htmldoc              No htmldoc, means no PDFs
        -S    --force-https             Force HTTPS redirect
        -C    --recreate-CA             Recreate the CA Keys
        -K    --recreate-keys           Recreate the SSL Keys
        -Y -y --autoaccept              Auto accept defaults and install
        -f    --file                    Use different update file
              --uninstall               Uninstall FOG

The uninstall option does not work yet, though there is some work towards starting it, it does not do anything directly yet.

The autoaccept option does operate. It should even operate for installs, though if it can’t find the proper defaults, it will ask for information.

The force-https has been added for quite some time. It basically will make your access to the fogserver point to https: rather than just giving you http.

The recreate-CA option creates the Certificate Authority. This is what’s installed with the new client install that enables the Client to know it can trust the FOG Server.

The recreate-keys item just recreates your private key if you should need it.

The file option requires a file if you’re going to use it. This is where you can use a different update file, or specify one if you’re fresh installing, but don’t want to retype all the values.

Hopefully this helps you all.

Logging is redirected but no more from a hidden file. It still happens as it did before, but it’s smarter I think.

[Joe Schmitt]

Just a heads up, calling recreate CA will cause all beta clients deployed to stop trusting your FOG server and will require a re-installation of the client / re-imaging.