Topics created by kek

@kek Just a quick update as I got to work allowing the fog-client to use a simple local CA certificate file instead of the mono keystore stuff. Would you be interested to test?

@Sebastian-Roth Thank you very much for your help! After you pointed me to the right file, i found a very easy and good working solution.

/var/www/html/fog/lib/fog/fogbase.class.php:

Changed line 2305 from:

$size = filesize($file);

to:

$size = exec("stat -c %s ".$file);

I found this nice solution over here:

stackoverflow

Reverted my changes that i showed in the last post, restarted FOGImageReplicator service, and it works perfect!

We know that this can’t work for forever, and Updates are also nice and good, so we need to change a few internal things, and also reinstall this Server with x64 Debian.

Thanks for your great support. Keep up this very very nice project!

I’m sorry I haven’t answered for so long, but I’ve been busy a lot and haven’t been able to address this issue until now.

First i only got the login of the FOG local users to work with the solution provided by @Tom-Elliott.
I could login with usernames the contain spaces with the following changes:

user.class.php:
Line 214:
Change the relevant regex from:

(?=^.{3,40}$)^[\w][\w0-9]*[._-]?[\w0-9]*[._-]?[\w0-9]+$

to:

(?=^.{3,40}$)^[\w][\w0-9]*[ ._-]?[\w0-9]*[ ._-]?[\w0-9]+$

fog.user.js
Comment out:

//regex: /^[\w][\w0-9]*[._-]?[\w0-9]*[.]?[\w0-9]+$/

When i tried to login with a domain user that contains spaces (users without spaces worked already) i got the same problem, no error but no login.

Then i figured out that the LDAP plugin uses the same check and regex so i had to edit this too:

ldap.class.php
Comment out:

/** * Test the username for funky characters and return * immediately if found. */ // $test = preg_match( // '/(?=^.{3,40}$)^[\w][\w0-9]*[._-]?[\w0-9]*[.]?[\w0-9]+$/i', // $user // ); // if (!$test) { // return false; // }

Now it works like a charm. 😃

Thanks to all people that were involved in this.

This can be marked as solved.

@Sebastian-Roth Thank you for your help, sorry for the late reply was very busy in the last weeks.
I managed it with turning on/off the no menu option.

you’ll want to edit the default storage node info on the storage management page to change these settings.
i have never used clonezilla, but it might be more in line with what you want

There are a couple of place’s you’d need to edit whether you choose to edit the init.gz, or edit the php file.

Editing the init.gz would work, but is more difficult as it requires unzipping, then mounting, editing, then unmounting, then rezipping all to check if your edit’s worked. If you made a mistake, you have redo the same steps over again. Repeat until all is working as expected. All of these steps would also require rebooting the system to check that the changes work as otherwise they’ll have the previous iteration of the init.gz loaded.

Editing the service scripts is probably easier, as you don’t have reboot the client to test, and they’res no unzipping, mounting, etc…

The easiest recommendation I could give for you to successfully do this is kind of two stepped.
First, manually create a false task entry in the database with something along the lines of:
[code]INSERT INTO fog.tasks (taskHostID,taskStateID) VALUES (‘1999’,‘1’);[/code]

Create a false Host entry using the fake ID you’ve set in tasks:
[code]INSERT INTO fog.hosts (hostID,hostMAC) VALUES(‘1999’,‘00:00:00:00:00:00’);[/code]

Then edit the Post_Stage2, Post_Stage3 and Pre_Stage1 files to leave the tasking alone if the host ID equals 1999 (or whatever false host you’ve given.

Then edit your default file to use the MAC Address 00:00:00:00:00:00 mac address.

I’m not giving specific instructions on editing the Post_Stage2, Post_Stage3, and Pre_Stage1 files because I don’t know what version of FOG you’re using, so I can’t provide an direct assistance.

That all said, while this all looks like a lot to have to do, it’s ultimately much simpler than editiing the init.gz. You didn’t want to have to create a task all the time, and with this you wouldn’t have to, just forcibly create the one task, and use that task as the “controller” for those extra entries.