General

• J

  [HELP WANTED] Client Internationalization
  • Joe Schmitt  

  45
  2
  Votes
  45
  Posts
  9469
  Views

  S

  @scosta Thanks! Will add this. Just have not had the time to do so and not sure when that will be. But be assured, this is not lost.
• J

  Firewall Configuration
  • Joe Schmitt  

  23
  2
  Votes
  23
  Posts
  12328
  Views

  

  the firewalld configuration no longer works on Fedora 21. The commands succeed, but at least http is blocked still.
• J

  SELinux Policy
  • Joe Schmitt  

  19
  2
  Votes
  19
  Posts
  14464
  Views

  

  Bumping this - it would be so nice to have SELinux enabled as a standard configuration.
• C

  FOG Status
  • Chuck Syperski  

  59
  0
  Votes
  59
  Posts
  33603
  Views

  

  Nope it’s still heavily in the beta phase, I bet when we do have an idea we will post it on the forums or on the main site letting everyone know we are close. There is a thread you are more than welcome to monitor it can be located here ->[url]http://fogproject.org/forum/threads/latest-fog-0-33b.6476/[/url]
• 

  Performance Monitoring tools
  • Fernando Gietz  

  8
  0
  Votes
  8
  Posts
  36
  Views

  

  Another tool to monitoting apache activity is apachetop. This tool gives you more info than modStatus
• 

  Site Plugin
  • Fernando Gietz  

  16
  3
  Votes
  16
  Posts
  2328
  Views

  

  @ragnurenson so, I’ve just tested after applying the commited changes and everything works fine! Thank you for pointing out the github commit and thanks @Fernando-Gietz for the awesome work! If I can make a suggestion, I’d say it would be nice to have that search filter implemented in “List All Hosts” screen on Active Tasks!
• 

  New FOG Testing dashboard. Feedback?
  • Wayne Workman  

  13
  2
  Votes
  13
  Posts
  353
  Views

  

  I made the changes and did a test run, dev-branch completely passed.
• S

  Circumnavigate fog user issues
  • Sebastian Roth  

  21
  3
  Votes
  21
  Posts
  370
  Views

  S

  Thinking a bit more about this I reckon we don’t really want to fully lock that account. It might even cause more people to ask in the forums. Better we try to inform the user as soon as we detect someone is using the account. And I mean informing beginners in particular. So for me it boils down to a couple of places we need to check and take care to inform the user. Fresh install - check if account already exists and setup a new account for the user in case it does - prompting for name and password and explaining why we do this. Upgrade with .fogettings (and therefore fog account) existing - check if the account was ever used to login on the machine (last | grep "^fog" and lastlog -u fog should do the job) and again setup a new account for the user - prompting for name and password and explaining why we do this. Print out a message to the user when opening a shell/terminal or login as fog user (~/.bashrc seems most appropriate to me) Print a X dialog when a user logs in as fog user (~/.config/autostart/ seems to be standard, works great with Ubuntu - anyone can try other distros as well?) mkdir -p /home/fog/.config/autostart/ cat >/home/fog/.config/autostart/warnfogaccount.desktop <<EOF [Desktop Entry] Type=Application Name=Warn users using the fog account Exec=/opt/fog/warnfogaccount.sh Comment=Warn users who use the fog system account to logon EOF chown fog:fog /home/fog/.config/autostart/warnfogaccount.desktop cat >/opt/fog/warnfogaccount.sh <<EOF #!/bin/bash title="FOG account" text="You seem to be using the 'fog' system account to logon and work \non your FOG server system.\n\nIt's NOT recommended to use this account! Please create a new \naccount for administrative tasks.\n\nIf you re-run the installer it would reset the 'fog' account \npassword and therefore lock you out of the system!\n\nTake care, \nyour FOGproject team" z=$(which zenity) x=$(which xmessage) n=$(which notify-send) if [[ -x $z ]] then $z --error --width=480 --text="$text" --title="$title" elif [[ -x $x ]] then echo -e $text | $x -center -file - else $n -u critical "$title" "$(echo $text | sed -e 's/ \\n/ /g')" fi EOF chmod 755 /opt/fog/warnfogaccount.sh
• 

  1.6 Hooks and their relevant Tie Ins
  • Tom Elliott  

  1
  2
  Votes
  1
  Posts
  91
  Views

  No one has replied

• 

  just sharing an appreciation post
  • Junkhacker  

  1
  6
  Votes
  1
  Posts
  80
  Views

  No one has replied

• 

  Help with code: usernotinme list
  • Fernando Gietz  

  8
  0
  Votes
  8
  Posts
  180
  Views

  

  Unless, of course, you’re trying to make it core usable? But the only time this would be viable would be if LDAP plugin is in use. Of course other plugins may want to make adjustments here as well. I need to think on this a little bit.
• 

  Fog Installer - Distro check
  • Wayne Workman  

  103
  3
  Votes
  103
  Posts
  14539
  Views

  

  @Sebastian-Roth Debian 9’s log appears here: /var/log/php7.0-fpm.log I’m going to have to match it like /var/log/php*-fpm.log and hope that does it.
• 

  RHEL 7 test
  • Wayne Workman  

  7
  0
  Votes
  7
  Posts
  120
  Views

  S

  Thanks to Wayne I had access to the RHEL 7 machine for a quick test and seems like we hit it with the latest fix. Installer went through like a charm. So RHEL is back in the race I suppose.
• J

  HOSTS EXPORT
  • jrm  

  3
  0
  Votes
  3
  Posts
  207
  Views

  J

  @Sebastian-Roth Thanks for you answer, i’ll try next time. Sincerely. Jérôme
• D

  RHEL 7.5 fresh install
  • Doctrg  

  4
  0
  Votes
  4
  Posts
  184
  Views

  S

  @Doctrg You should be able to go straight from 1.3.5 to 1.5.4 I think. Make a full DB dump on the old server, install mysql on the new one by hand (yum install mysql mysql-server), import DB dump and then start the FOG 1.5.4 installer. When it asks you to open the web interface go ahead and it should upgrade your database structure - usually does without an issue. Not saying there can’t be anything going wrong but mostly this is going fine. As you still have the old server (or at least a full backup of machine and DB), you can always give it a try. Shouldn’t hurt.
• P

  F.O.G on windows server
  • princz  

  12
  0
  Votes
  12
  Posts
  10746
  Views

  V

  @tom-elliott we do all the installing manually… Could you please elaborate the steps…
• S

  Postdownload Scripts
  • SHerder  

  3
  0
  Votes
  3
  Posts
  291
  Views

  J

  Like @Tom-Elliott said, the initial postdownload script always runs. However, you can use CASE or IF statements to either call a function or open another script. Here is my current postdownload script that I got from one of @george1421 and his wonderful driver injection scripts found here #!/bin/bash . /usr/share/fog/lib/funcs.sh [[ -z $postdownpath ]] && postdownpath="/images/postdownloadscripts/" if [ $img == "Win7BaseVM" ] || [ $img == "Win10BaseVM" ] ; then case $osid in 5|6|7|9) clear [[ ! -d /ntfs ]] && mkdir -p /ntfs getHardDisk if [[ -z $hd ]]; then handleError "Could not find hdd to use" fi getPartitions $hd for part in $parts; do umount /ntfs >/dev/null 2>&1 fsTypeSetting "$part" case $fstype in ntfs) dots "Testing partition $part" ntfs-3g -o force,rw $part /ntfs ntfsstatus="$?" if [[ ! $ntfsstatus -eq 0 ]]; then echo "Skipped" continue fi if [[ ! -d /ntfs/windows && ! -d /ntfs/Windows && ! -d /ntfs/WINDOWS ]]; then echo "Not found" umount /ntf >/dev/null 2>&1 continue fi echo "Success" break ;; *) echo " * Partition $part not NTFS filesystem" ;; esac done if [[ ! $ntfsstatus -eq 0 ]]; then echo "Failed" debugPause handleError "Failed to mount $part ($0)\n Args: $*" fi echo "Done" debugPause . ${postdownpath}fog.deletelog . ${postdownpath}fog.drivers #. ${postdownpath}fog.ad umount /ntfs ;; *) echo "Non-Windows Deployment" debugPause return ;; esac fi You can see that I have an if statement at the beginning to only run his driver injection script if the image name is one of my golden image VM’s.
• 

  7156 ipxe binaries question
  • Wayne Workman  

  3
  2
  Votes
  3
  Posts
  273
  Views

  

  Removed. Well, kept the surface-pro-4 matching element, but just removed the 7156 portion.
• M

  FOG API returning 404
  • maikBat  

  6
  0
  Votes
  6
  Posts
  335
  Views

  

  @maikbat by default the api access is disabled. Check fog configuration ->fog settings->API Settings and enable
• A

  FOG must expand multiple OS, including Windows servers!
  • avandel  

  8
  0
  Votes
  8
  Posts
  666
  Views

  A

  @wayne-workman Says the man with an aintient electonictube as picture…(-: I am too old to pick that stuff up now, been trying that on and off for the last 10 years, as i told you, it doesn’t stick to me… And I am happy for you people who can master Linux, I envy you that it comes to you easier than to me… I really do not know how to get started to solve my problem… So, it is google all the way for me… Thanks for sticking around and actually add something usefull to the community, I on the other hand am to stupid to help! (I think…)