Latest FOG 0.33b
-
I already did them. Why?
-
r1375 released.
Updates more documentation. Also updates the TomElliott.config files for 3.13.7.
-
[quote=“Tom Elliott, post: 24596, member: 7271”]I already did them. Why?[/quote]
So I can test the scheduled task with as master storage has external SAN like Synology ? -
Sure.
-
[quote=“Tom Elliott, post: 24602, member: 7271”]Sure.[/quote]
it works very well !!
-
[quote=“Tom Elliott, post: 24602, member: 7271”]Sure.[/quote]
I have just one last problem : as I said the SYNOLOGY or IOMEGA put before their NFS shares a name like “[B]volume1[/B]” or “[B]nethdd[/B]” while sharing the same FTP did not !
For the same share on SYNOLOGY:NFS : /volume1/imagesFTP : /imagesThe problem after the backup operation when ftp_delete and ftp_rename.
So I added before line 57 in / var/www/html/fog/service/Post_Stage2.php
[CODE]
// SYNOLOGY —
if(stripos($dest, ‘volume1’) !==false){
$src = str_replace(“/volume1/”, “/”, $src);
$dest = str_replace(“/volume1/”, “/”, $dest);
// IOMEGA —
if(stripos($dest, ‘nethdd’) !==false){
$src = str_replace(“/nethdd/”, “/”, $src);
$dest = str_replace(“/nethdd/”, “/”, $dest); }
[/CODE]
And replaced the function delete($path) in /var/www/html/fog/lib/fog/FOGFTP.class.php because SYNOLOGY do not like the “[B]ftp_nlist[/B]” function but rather “[B]ftp_rawlist[/B] "
[CODE]
public function delete($path)
{
if (!(@ftp_delete($this->link, $path)||@ftp_rmdir($this->link,$path)))
{
$filelistraw = $this->ftp_nlist_Syno($this->link,$path);
$filelist = (array_keys($filelistraw));
if ($filelist[0]){
foreach($filelist AS $file)
{
$this->delete($path.”/".$file);
}
$this->delete($path);
}
}
// Return
return $this;
}public function ftp_nlist_Syno($resource, $directory) { if (is_array($children = @ftp_rawlist($resource, $directory))) { $items = array(); foreach ($children as $child) { $chunks = preg_split("/\s+/", $child); //$item['type'] = $chunks[0]{0} === 'd' ? 'directory' : 'file'; array_splice($chunks, 0, 8); $items[implode(" ", $chunks)] = $item; } return $items; } // Throw exception or return false < up to you }[/CODE]
[COLOR=#3366ff]There he has a way to solve this problem ?[/COLOR]
[url=“/_imported_xf_attachments/0/610_Capture.JPG?:”]Capture.JPG[/url]
-
I didn’t design IOMEGA or SYNOLOGY NAS Systems. So it’s beyond me how and/or why you can’t use the true paths properly.
-
The problem is the FTP step (rename and delete) why not just do these steps in NFS ?
-
So what’s wrong with the FTP Step? If I understood your previous post, FTP to those directories removes the /volume1/ label and sets the home to /volume1/ making the ftp step look at /images through relative means. I didn’t configure there FTP server, so I don’t know how to help. The reason for not doing it via NFS is because of permissions.
-
This post is deleted! -
Hello,
just for report:
blank page when i update an option in the service configuration page.(but the change is ok )
Apache Log:
PHP Fatal error: Call to a member function set() on a non-object in /var/www/fog/lib/pages/ServiceConfigurationPage.class.php on line 307The fog FOGMulticastManager don’t start. I have to do chmod +x on the /opt/fog/service/FOGMulticastManager/FOGMulticastManager
Fog Rev :1377
I will try imaging this morning (french hours !!!
)
Voila!!! -
Just a question:
how to for the FOG_KEY_SEQUENCE ?
-
r1378 released.
Should fix the service configuration page error reported above. A couple of minor fixes to Imaging Log report page.
@lepretre: Can you give more information about your question? Are you wondering what it is? How to use it? I don’t know.
-
Thanks Tom
For the the FOG_KEY_SEQUENCE ?
What kind of key combination can I use?
Can I have an example of the parameter to write?Olivier
-
It’s on the PXE Settings screen. It show’s the key combination that you would use to get to the menu. it’s only active when the Hidden Menu checkbox is checked.
-
r1383 released.
Moves Imaging Log to class file, for the time being it will display like normal, until I get all the default reports moved into the report class as their own objects, I’m leaving these files.
-
[quote=“Tom Elliott, post: 24618, member: 7271”]So what’s wrong with the FTP Step? If I understood your previous post, FTP to those directories removes the /volume1/ label and sets the home to /volume1/ making the ftp step look at /images through relative means. I didn’t configure there FTP server, so I don’t know how to help. The reason for not doing it via NFS is because of permissions.[/quote]
Can we still correct code “[B]ftp_nlist[/B]” with a code “[B]ftp_rawlist[/B]” in “/var/www/html/fog/lib/fog FOGFTP.class.php” which seems to be more compatible with different NAS server?
-
What is the difference between nlist and rawlist?
What would happen if I just did basename to the path being sent? Would this, theoretically, work properly as the basename of /volumes1/images would be images and the basename of /images would also be images?
The only issue I see with using basename is for those file systems where you need the full path for things to work. I believe this is why nlist was used. It allows you to read the contents within a specified directory. I’m still under the impression that the NAS boxes just need to be configured so /volume1 is not where it plops you in for FTP. It should be relatively simple, though I don’t have a NAS to test with.
-
Hy,
not working When i deploy image type “other” with multos windows + linux .(upload ok)
I try in debug deploy and nothing is done after update database:Rev: 1378
[IMG]http://olivierlepretre.free.fr/CAM00110.jpg[/IMG] -
@lepretre
I guess I’m confused? What do you mean nothing is done after the database is update?
Are you saying it doesn’t actually image the system? Are you saying it doesn’t reboot?I’m guessing you’re saying it doesn’t actually deploy the image. I can try to take a look into that, but I don’t have a system to test with readily available, so I’m sorry if it’s a little delayed.
When you say image type, are you referring the “Single Disk (Resizable), Multi Part Single/All Disk (Non-Resizable), Raw” or the OS Type as “other”?
