Your default file (that’s the name sorry) is located at:
/tftpboot/pxelinux.cfg/default
On the bottom line you should see:
[code]TIMEOUT 30[/code]
This means 3 seconds. Thirty seconds would be:
[code]TIMEOUT 300[/code]
I
Your default file (that’s the name sorry) is located at:
/tftpboot/pxelinux.cfg/default
On the bottom line you should see:
[code]TIMEOUT 30[/code]
This means 3 seconds. Thirty seconds would be:
[code]TIMEOUT 300[/code]
I
Ownership of /tftpboot should be:
[code]sudo chmod -R 755 /tftpboot
sudo chown -R fog:root /tftpboot[/code]
It doesn’t like firewalls, but there’s a writeup somewhere firewall setup and FOG. Maybe try [url]http://fogproject.org/forum/threads/firewall-config.27/#post-16286[/url]
No you shouldn’t have to. There should be a value for timeout after a number of seconds.
Is the next-server line in your dhcp address pointing at your FOG Server?
VincentJ,
Does hostname changer work with the FOG Client installed? I ask because I know the early hostname changer is working for XP, I’m still not sure on Windows 7 though as I’ve been working on fixing actual problems rather than tinkering with this little nuisance. Not that I’ve forgotten about it, just been busy trying to get other elements operating for people.
I’ll have to rebuild and let you know. I started out trying that, but it didn’t seem to want to work properly, so I removed it. I’ll add it and let you know.
I forget one thing.
Try this:
[code]service rpcbind restart
service nfs restart[/code]
NFS Should then be running.
does this new location have .mntcheck files:
[code]
sudo touch /images/.mntcheck
sudo touch /images/dev/.mntcheck[/code]
Also check that your ftp information operates as expected as well. The storage username and password should be that of the FOG Servers (or storage nodes) fog user (on the server/node) not the database username and password.
MAC’s are supported as I’ve added the binaries to the init.gz, though I think this will have to be manual for the time being. I’ll have to add the MAC os to the OS Listing and have it translated to allow for hfs imaging.
r1095 released. Fixes space in the UDP part as stated in the BUGS forum.
But running PHP 5.4 or later. I can tell by this line:
Call-time pass-by-reference has been removed in /var/www/fog/management/includes/tasks.confirm.include.php on line 754, referer: [url]http://localhost/fog/management/index.php?node=host&sub=edit&tab=tasks&id=1[/url]
The reference has to be adjusted.
Go to your fog webdir. Probably at:
/var/www/fog (UBUNTU TYPICAL)
OR
/var/www/html/fog (REDHAT TYPICAL)
Run this command:
[code]grep -rl ‘&$tmp’ .[/code]
In the files that display after this, edit them and remove the & symbol from the $tmp variables. So the variable will change from:
[php]&$tmp[/php]
to
[php]$tmp[/php]
I’m guessing you’re using FOG 0.32?
Sorry about the previous formatting, hopefully this fits the bill for you.
[code]httpd php php-cli php-common php-gd php-mysql mysql mysql-server dhcp tftp-server nfs-utils vsftpd net-tools wget xinetd tar gzip make m4 gcc gcc-c++ htmldoc perl perl-Crypt-PasswdMD5 lftp clamav[/code]
[code]service xinetd restart
service nfs restart[/code]
[code]#where is freshclam’s config file
#freshdb=“/var/lib/clamav/”;
freshdb=“/var/clamav/”;
freshwebroot=“${webdirdest}/av/”;
freshconf=“/etc/freshclam.conf”;
#freshcron=“/etc/sysconfig/freshclam”
freshcron=“/usr/bin/freshclam”[/code]
LOSE THE COLOR STUFF, it added it for some unknown reason.
try changing your lib/redhat/config.sh lines for install packages to this:
[code]httpd php php-cli php-common php-gd php-mysql mysql mysql-server dhcp tftp-server nfs-utils vsftpd net-tools wget xinetd tar gzip make m4 gc c gcc-c++ htmldoc perl perl-Crypt-PasswdMD5 lftp clamav[/code]
[COLOR=#000000]AND Where appropriate[/COLOR]
[COLOR=#000000][code]httpd php php-cli php-common php-gd php-mysql mysql mysql-server dhcp tftp-server nfs-utils vsftpd net-tools wget xinetd tar gzip make m4 gc c gcc-c++ htmldoc perl perl-Crypt-PasswdMD5 lftp clamav[/code][/COLOR]
[COLOR=#000000]Then change the freshclam lines to:[/COLOR]
[COLOR=#000000][code]#where is freshclam’s config file[/COLOR]
[COLOR=#000000]#freshdb=“/var/lib/clamav/”;[/COLOR]
[COLOR=#000000]freshdb=“/var/clamav/”;[/COLOR]
[COLOR=#000000]freshwebroot=“${webdirdest}/av/”;[/COLOR]
[COLOR=#000000]freshconf=“/etc/freshclam.conf”;[/COLOR]
[COLOR=#000000]#freshcron=“/etc/sysconfig/freshclam”[/COLOR]
[COLOR=#000000]freshcron=“/usr/bin/freshclam”[/code][/COLOR]
[COLOR=#000000]To fix the NFS issues, you will have to manually enter these commands:[/COLOR]
[COLOR=#000000][code]service xinetd restart[/COLOR]
[COLOR=#000000]service nfs restart[/code][/COLOR]
[COLOR=#000000]Then you should be good to go.[/COLOR]
You’re working with 0.32.
Remove the php-gettext from the lib/redhat/config.sh file. php-common installs php-gettext for you.
I believe the udp-sender is performed by the FOGMulticastManager service found in /opt/fog/service/FOGMulticastManager and started with the command:
[code]sudo service FOGMulticastManager restart[/code]
I’m going to ask, are you using FOG 0.32 or FOG 0.33b?
I think this problem is still existing in FOG 0.33b as I haven’t added anything for gparted, though I imagine this is relatively easy to do. I’m just one guy though, so making all these edits and testing is a bit rough. I’ve basically been trying to get things back to a sort of operational state from the Perspective of the init.gz, kernel, and WEB GUI and have edited the fog scripts pretty heavily. However, theh things I do notice is that FOG doesn’t like anything more than three partitions. The problem, I imagine, is that the images are saved from partition to partition rather than disk to disk.
I don’t know if disk to disk is even possible so I’ll try playing with that today. If it goes disk to disk, I’d imagine imaging would be a little better off as we don’t need to loop through each of the files in a specified order to get things imaged. We only need the one file, but what implications this has on varying disk sizes is questionable.
Questions I ask myself are:
Would this method copy the data appropriately?
Does this mean your drives are resized according to the drive parameters?
Will this work for GPT/EFI/MBR?
Does partclone do disk copies in this manner with bit to bit, or block to block?
While these are just a couple of questions, I think these are the biggest of them all as we would need to know the implications of this.
What happens when you type:
[code]yum -y list all|grep php-gettext[/code]