Categories

  • 12k Topics
    114k Posts
    Tom ElliottT

    @Greg-Plamondon I’m going to try delving into this but I’ve been very busy with other things and just haven’t gotten around.

    I do appreciate the patience and assistance.

    The changes you were doing that fixed the problem, please implement them again and you should be back to functional

    Once that is done, do you mind doing a diff between that file and the relevant file in the git repository side:

    Files I think you changed were under: <path>/<to>/<installer>/packages/service/<servicename>/<servicefile>

    I’m not seeing any issues on my test systems.

    not really sure why it isn’t working either.

    I believe you were editing the files in /opt/fog/service/<servicename>/<servicefile>

    So you would do:

    diff -u <path>/<to>/<installer>/packages/service/<servicename>/<servicefile> /opt/fog/service/<servicename>/<servicefile>
  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    Cire3C

    @youzersef Ok, see how long it takes me to get back on a project…lol

    I did some more looking, and found yes, the GUI will re-write the dhcp config file. However I did some more reading and I guess services.inc determines what is written by the GUI.

    Sorry, not a CLI guy, and I love the quick and easy edits, viewing issues that the GUI provides. Like Fog ! However my servers are headless…lol

    Anyway, looking that route now, and will update if I find how Negate wants services edited so when it reboots, DHCP will remain.

    Determined 🙂

    Any thank you everyone here . This place has always been great for information !

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    M

    Okay - So what killled this installation was the fact a 1.5.9 csv load was imported into my 1.5.10.1698 FOG - this killed a bunch of features and I eded up having to reinstall.

123

Online

12.6k

Users

17.5k

Topics

156.3k

Posts